In my experience of working as a consultant and then as an Architect in product company, I find a common pattern when it comes to database adoption. A lot of people coming to product companies with relational database experience, find it very difficult to adapt to the way DynamoDB works.

This talk distills down my experiences into actionable insights of up-skilling myself and a lot of colleagues with relational database background to successfully adopt DynamoDB.

This talk focuses on three main topics -
1. The way DynamoDB operates differently
2. The effects of this differences in data modelling
3. Some ways one can adapt their thinking to reap the best benefits from DynamoDB.

I will cover a little theory of DynamoDB, introduce Domain Driven Design as a tool to find access patterns for your use case, touch on the topics of microservices as the method of successful adoption of cloud and DynamoDB and finally then walk though an example where I take a Relational database schema and convert it into Single Table Design for DynamoDB