3 ms·
> Is the dream of a self-managing, fire-and-forget key value database completely naive? It's not, if you plan it right. Learn about single table design for Dy
by jedberg 5y ago
> Is the dream of a self-managing, fire-and-forget key value database completely naive?
It's not, if you plan it right. Learn about single table design for DynamoDB before you start. There are a lot of good resources from Amazon and the community.
Here is a very accessible video from the community:
https://www.youtube.com/watch?v=BnDKD_Zv0og https://www.youtube.com/watch?v=BnDKD_Zv0og
Here is a video from Rick Houlihan, a senior leader from AWS who basically helps companies convert to single table design:
https://www.youtube.com/watch?v=KYy8X8t4MB8 https://www.youtube.com/watch?v=KYy8X8t4MB8
And a good book on the topic:
https://www.dynamodbbook.com https://www.dynamodbbook.com
If you use single table design, you can turn on all of the auto-tuning features of DynamoDB and they will work as expected and get better and more efficient with more data.
Some people worry that this breaks the cardinal rule of microservices: One database per service. But the actual rule is never have one service directly access the data of another, always use the API. So as long as your services use different keyspaces and never access each other's data, it can still work (but does require extra discipline).