At the Distributed SQL Summit 2020, Tobias Meixner – CTO & Co-Founder at BRIKL, presented the talk, “A Migration Journey from Amazon DynamoDB to YugabyteDB and Hasura.”
Switching databases is painful, even more so when going from NoSQL to SQL. In this talk Tobias gave us insights into BRIKL’s two key elements of their migration path. First, migrating from Apollo Server and Amazon DynamoDB over to Hasura and YugabyteDB.
…
The SQL vs. NoSQL database split emerged in 2006-2007, but NoSQL’s compromises led developers to continue using SQL/RDBMS for critical workloads. However, recent changes in the NoSQL world have seen the adoption of ACID transactions, which were previously absent, and this post aims to inform architects of these changes and why they are happening now.
DynamoDB is AWS’s NoSQL alternative to Cassandra, primarily marketed to mid-sized and large enterprises. It works best for those who require a flexible data model, reliable performance, and the automatic scaling of throughput capacity. In a nutshell, DynamoDB’s monthly cost is dictated by data storage, writes and reads. Let’s walk through a synopsis.
This post is to help developers and operations engineers understand the precise strengths and weaknesses of DynamoDB, especially when it needs to power a complex, large-scale application.