How to Decide When It’s Right For You
Important Note. Since this article was originally published, AWS has added several new features to DynamoDB including adaptive capacity, on-demand backups, and point in time recovery. While many points in this article are still valid, some may be out of date. Please consult the latest DynamoDB documentation before making any technology decisions.
By 2004, Amazon’s business was already stretching the limits of their Oracle database infrastructure. In order to scale the growing business, AWS designed an award winning internal key-value store — Amazon Dynamo — to meet their performance, scalability, and reliability requirements.
Amazon Dynamo now underlies much of Amazon.com and defined an entirely new category of key-value store databases — “NoSQL”. In 2012, AWS announced the availability of DynamoDB as a fully managed NoSQL data service to customers with the promise of seamless scalability.
Why use DynamoDB?
As Dynamo celebrates its tenth anniversary, AWS should consider a companion service called “WhynamoDB”. Every time a developer attempts to provision a new DynamoDB table, the service would pop-up in the AWS Console and simply ask: “Why?”
The answer to “why use DynamoDB” isn’t as straightforward as the marketing promise of seamless scalability and cloud enablement initiatives.
Over the past few weeks, I interviewed a number of engineers and developers about their experiences with the AWS database services. As great as DynamoDB is — and as rousing as its success stories are — it has also left plenty of failed implementations in its wake.
There are very few suitable use cases for DynamoDB | Hacker News — Fundamentally, the problem seems to be that choosing a partitioning key that’s appropriate for DynamoDB’s operational — news.ycombinator.com
In order to understand what causes some DynamoDB implementations to succeed and others to fail, we need to examine the essential tension between DynamoDB’s two great promises — simplicity and scalability.
DynamoDB is Simple — Until it Doesn’t Scale
I really can’t overstate how easy it is to start throwing data in DynamoDB. The AWS team has done a great job of abstracting away complexity — you don’t have to log into a management studio, you don’t have to worry about database drivers, you don’t have to set up a cluster.
To get started with DynamoDB, just turn a knob for provisioned capacity, grab your favorite SDK, and start slinging JSON.
With that feature set, it’s no wonder that DynamoDB is especially attractive to “serverless” application developers. After all, a lot of serverless apps start as prototypes, prioritizing speed of delivery and minimal configuration. Why mess with a relational datastore when you don’t even know yet what your final data model is going to look like?
Designing a DynamoDB-backed Architecture is Not Easy
At this point, we need to make a key distinction — no pun intended. DynamoDB may be simple to interact with, but a DynamoDB-backed architecture is absolutely not simple to design.
DynamoDB is a key-value store. It works really well if you are retrieving individual records based on key lookups. Complex queries or scans require careful indexing and are tricky or straight-up inadvisable to write — even if you don’t have a terribly large amount of data, and even if you have some familiarity with NoSQL design principles.
That last part is the kicker, of course — there are an awful lot of developers who don’t know much about NoSQL compared to classic relational database design. Moreover, prior NoSQL experience isn’t always a net positive. I spoke to a few engineers whose teams were burned when they brought a bunch of expectations from MongoDB, a document database, to their DynamoDB implementation.
So when you combine inexperienced devs, the lack of a clear plan for how to model a dataset in DynamoDB, and a managed database service that makes it really easy to ingest a lot of unstructured data — you can end up with a solution that spirals out of control even at a small scale.
Lynn Langit, a cloud data consultant with experience in all three of the big public clouds, has seen enough of these botched implementations to be justifiably wary of businesses relying on NoSQL solutions like DynamoDB.
When I interviewed Lynn recently for the “Serverless Superheroes” series, she shared a story about moving a client from DynamoDB to Aurora — the Amazon Aurora Serverless Data API — even though the AWS reference architecture for their project used DynamoDB.
“The client was having all sorts of problems, and one day I just decided to switch to Aurora. Freaked out everybody — they said, ‘What are you doing?’ I said, ‘What are we doing? We’re shipping a product.’ And we did.”
The First Law of DynamoDB: Assume that a DynamoDB implementation will be harder not, not easier, than using a rational database that you already know.
A relational database will do most anything you need at small scale. It might take a little longer to set up initially than DynamoDB, but the well-established conventions of a SQL implementation can protect you from a lot of wasted time down the road.
This isn’t because DynamoDB is worse technology — but because it is new to you, and things that seem “easy” and “convenient” will absolutely bite you if you do not understand them.
Which NoSQL DB is the GOAT? See which database service reigns supreme in all the cloud between AWS DynamoDB vs GCP Cloud Datastore and Bigtable vs Azure Cosmos DB.
DynamoDB is Scalable — Until it Isn’t Simple
Now explore the other end of the spectrum — great big DynamoDB tables. For this article I interviewed happy customers getting sub-second latency with billions of records in their DynamoDB tables. DynamoDB promises consistent performance at essentially infinite scale, limited only by the physical size of the AWS cloud.
Without exception, these customers are right in the center of DynamoDB’s canonical use case — doing key-value lookups on well-distributed records, avoiding complex queries, and most importantly, limiting hot keys.
Dealing with hot keys is undoubtedly DynamoDB’s best-known “gotcha”. The issue with hot keys is well explained in many places including the DynamoDB developer’s guide documentation.
Best Practices for Tables – Amazon DynamoDB — Use these best practices for working with tables items to get the best performance with reduced throughput costs using — docs.aws.amazon.com
Although DynamoDB can scale indefinitely, your data isn’t stored on a single, magic, ever-expanding server. As your data grows larger than the capacity of a single DynamoDB shard, or “partition” (up to 10 GB), it gets divided into chunks, with each chunk living on a different partition.
If you have a “hot” key in your dataset — a particular record that you are accessing frequently — you need to be sure that the provisioned capacity on your table is set high enough to handle all those queries.
The “gotcha” is that you can only provision DynamoDB capacity at the level of the entire table — not per partition — and the capacity is divided up among the partitions using a fairly wonky formula. As a result, your read and write capacity on any given record is a lot smaller than your overall provisioned capacity.
So if your application is using too many RCUs on a single key, you either need to over-provision all the other partitions (expensive), generate a ton of “Throughput Exceeded” errors (not ideal), or figure out how to decrease access to that key.
One takeaway here is that DynamoDB isn’t necessarily suited to datasets that have a mix of hot and cold records. But at sufficiently large scale, every dataset has such a mixture. You could split up the data into different tables, of course — but if you do that, you’ve lost the scalability advantage that DynamoDB was supposed to be providing in the first place.
A blog was recently published on this subject called “The Million Dollar Engineering Problem”. It showed how Segment substantially decreased their AWS bill by fixing hot key-related DynamoDB over-provisioning. The most interesting part of that article is the “heatmap” graphics showing exactly which partitions were the troublemakers.
Now, if you read the fine print, those cool graphics came from AWS’s internal tools, not from any monitoring Segment was able to do on their own. In other words, somebody from Segment had to get on the phone with the DynamoDB team in order to get observability into their database problems.
Even at that point, their strategy for blocking the offending keys was a matter of wrapping DynamoDB calls in a try/catch — and executing custom trace logic if a particular key tripped a throughput exception.
In effect, Segment had to fight the hot keys problem with a blindfold on, and this is where we get back to the tension between simplicity and scale.
DynamoDB is designed as a black box with very few user-accessible controls. This approach makes it easy to use when you are just getting started. But at production scale — when edge cases rule your life — sometimes you desperately need more insight into why your data is misbehaving.
You need a little bit of compassionate complexity.
The Second Law of DynamoDB: At massive scale, DynamoDB’s usability is limited by its own simplicity.
This is not a problem with the architecture of Dynamo. It’s a problem with what AWS has chosen to expose through the service of DynamoDB.
At this point, we haven’t even touched on the issue of backups and restores — something DynamoDB doesn’t support natively and which gets awfully tricky at scale. The inability to back up 100TB of DynamoDB data was apparently a big reason why Timehop recently moved off the service altogether.
If Not DynamoDB, Then What?
So if DynamoDB is just one of many plausible options at small scale, and has limited viability as a service at large scale — what is it good for?
If you ask AWS, almost anything. After all — Werner Vogels says the original Dynamo design could handle about 90% of Amazon.com’s workloads.
With the exception of certain special cases like BI analytics or financial transactions, it’s true that you can redesign just about any application to move the business relationships out of the database, store state in a K/V table, and use event-driven architecture to your heart’s content.
But as my computer science professor used to say, it’s also true that “just because you can, doesn’t mean you should.”
If you don’t fully understand why you are using DynamoDB at the outset, you’re likely to end up like Ravelin spinning your wheels through several code rewrites until finally landing on a solution that more or less works — but you still kind of hate.
You probably shouldn’t use DynamoDB — Avid readers of the Ravelin syslog will remember a story from last year about our use of DynamoDB. It outlined a few — syslog.ravelin.com
The Third Law of DynamoDB: Business value trumps architectural idealism every time.
This is why Lynn Langit has more or less abandoned NoSQL as a solution for small and medium-size businesses. It’s why Timehop moved from DynamoDB to Aurora, and why another well-known company I interviewed has moved to “a giant ElasticSearch cluster”.
It’s also why DynamoDB has gobs of case studies from satisfied customers at famous brands. Not because one of these technologies is uniformly better than another — but because the engineers in each company, with their specific use cases and levels of expertise, were able to deliver business value most quickly and effectively with differing solutions.
At some point, Amazon may announce the release of the WhynamoDB service that asks “why you are provisioning a DynamoDB table”. In preparation for the launch, I’ve created this handy decision tree that guides you through the WhynamoDB service.
Get the skills you need for a better career.
Develop cloud skills, get certified, and level up your career. Whether you’re just starting out or a seasoned pro, you can learn by doing and advance your career in cloud with ACG.
If you enjoyed this article, be sure to follow me Twitter where I’m @forrestbrazeal.