This whitepaper is for historical reference only. Some content might be outdated and some links might not be available.
Considerations
Best practices and limitations
-
For implementation best practices and limitations, refer to the AWS documentation for the respective database service.
-
If your use cases use relatively static schemas, perform complex table lookups, require accessing data across multiple keys and might experience high service throughputs it might be a better fit for Amazon RDS
offerings.
Some customer journeys and lessons learned
-
Amazon DynamoDB on Production: FinBox’s Compilation of Lessons Learned in a Year
-
Refer to this case study
to learn how McAfee’s use case of migrating from Microsoft SQL server to DynamoDB to power their next generation messaging platform to drive ecommerce business -
Watch this video
on why Amazon Fulfillment choose Amazon DocumentDB to power their inventory authority platform (IAP), considerations for performance and scale, and some learnings from their experience -
Watch this video
to hear about FINRA ’s story on how they modernized their data collection platform used by FINRA customers from a relational database using XML to Amazon DocumentDB. -
Idea to product: PricewaterhouseCoopers launches Check-In within three months on Amazon Keyspaces
-
Watch this video
to learn about the key features of ElastiCache (Redis OSS) and dive deep into how Groupon uses ElastiCache for deal curation. -
Blog post
on how Near was able to reduce latency by four times and achieve 99.9% uptime of its critical RTB platform applications by moving to ElastiCache. -
LexisNexis
presentation on using graph to store relationships between legal documents using Amazon Neptune . -
Cox Automotive
presentation on using graph to store relationships between user identities on their web platforms to power marketing and advertising.
References
-
Scale and performance characteristics of Timestream
– Deriving near real-time insights over petabytes of time series data with Amazon Timestream. -
This blog post
provides you with a quick summary and set of resources for common topics so you can quickly ramp up on Amazon DocumentDB. -
This blog post
provides improved performance characteristics of Amazon Keyspaces, lightweight transactions API, advanced design patterns, and operational best practices. -
AWS Online Tech Talks: ElasticCache
best practices -
Getting started
with Amazon Neptune by creating a graph of all of your AWS resources. -
How to migrate an application
from using GridFS to using Amazon S3 and Amazon DocumentDB. -
Graph data model lets you traverse through relationships without requiring joins and indexes. For more information, refer to the "How Do I Know I Need an Amazon Neptune Graph Database?”
video. -
Graph data model lets you traverse through relationships without requiring joins and indexes. For more information, refer to "How Do I Know I Need an Amazon Neptune Graph Database?”
. -
Complex data models (such as arrays, nested fields, and deep relationships) let you consider a wider range of application needs. For more information, refer to the “When to use DocumentDB vs DynamoDB
” video. -
DynamoDB provides extreme scale for certain data access patterns. For more information, refer to “How to determine if Amazon DynamoDB is appropriate for your needs
”. -
Refer to this tech talk
to learn about DocumentDB use cases, and how Amazon DocumentDB cluster architecture provides better performance, scalability, and availability. -
Amazon MemoryDB is a durable, in-memory database for workloads that require an ultra-fast Redis-compatible primary database. If you require sub-millisecond performance and need to add persistence and durability, consider using MemoryDB rather than in-memory cache for Redis. Refer to this tech talk
to learn about Amazon MemoryDB.
Developer references
-
Why purpose-built database?
This hands-on tutorial will help you get an idea of how AWS NoSQL databases can help run your specific workloads.
Training and guidance
-
To ensure that development teams were comfortable with transitioning to Amazon, it essential to train the teams on AWS NoSQL databases and cloud-based design patterns (tech talks, workshops
, and Immersion Days .)