


In the end, we chose DynamoDB for a couple of key reasons: scalability, isolation, and flexibility. We explored a variety of different solutions from MongoDB Atlas, Apache Cassandra, and Couchbase. This model, which powers our fraud detection pipeline, was not relational and was growing rapidly due to the increasing number of transactions processed through Bolt. We had a variety of data models that naturally fit in a No-SQL paradigm, but our transaction risk data was a great first use case.

In late 2020, we set out to find a good No-SQL database to complement our Postgres DB. We chose DynamoDB over a variety of well established No-SQL technologies
