From what I've gleaned through speaking to current and former Amazon employees you basically have to use DynamoDB for all new services. IMHO the logical progre

From what I've gleaned through speaking to current and former Amazon employees you basically have to use DynamoDB for all new services. IMHO the logical progression for applications with typical relational models is starting with an RDBMS in combination with an ORM, breaking out of the ORM when necessary for more complex/slower queries, ditching the ORM altogether when it starts to break, then evaluating sharding or moving domains into a NoSQL solution piecemeal. A well-architected monolith or series of microservices suits this paradigm which allows you to realize the productivity benefits of SQL and only worry about the deduplication, indexing, and consistency issues that come with NoSQL when it becomes actually necessary. Then again if I were Amazon I'd probably plan for scale up front and be jaded by their experience with Oracle too.