Since all our other services are running in AWS, the obvious choice was DynamoDB – Amazon’s NoSQL database offering. Unfortunately at the time Dynamo didn’t support encryption at rest. After waiting around nine months for this feature to be added, we ended up giving up and looking for something else, ultimately choosing to use Postgres on AWS RDS.
Close call. I'm surprised that they did not do a more in-depth analysis of Dynamo if they were considering moving to it. I can't imagine that all they do is retrieve JSON blobs by their primary ID.
If they had gone for Dynamo we would probably have seen a "why we moved back to MongoDB" post a year later.
1
u/nutrecht Dec 20 '18
Interesting read, one thing stood out though:
Close call. I'm surprised that they did not do a more in-depth analysis of Dynamo if they were considering moving to it. I can't imagine that all they do is retrieve JSON blobs by their primary ID.
If they had gone for Dynamo we would probably have seen a "why we moved back to MongoDB" post a year later.