Yet data modeling with DynamoDB is tricky for those used to the relational databases that have dominated for the past few decades. There are a number of quirks around data modeling with DynamoDB, but the biggest one is the recommendation from AWS to use a single table for all of your records.
In this post, we’ll do a deep dive on the concepts behind single-table design. You’ll learn:
- What is single-table design
- Why single-table design is needed
- The downsides of single-table design
- The two times where the downsides of single-table design outweigh the benefits
Short backend is built on top of Uncle Bob’s Clean Architecture, the central objective of which is separation of concerns.
Short adopts Microservices Architecture to organize dependent services around business capabilities and to enable independent deployment of each service.
Short leverages Kubernetes to automate deployment, scaling, and management of containerized microservices.
Short is maintained by a small team of talented software engineers working at Google, Uber, and Vmware as a side project.