Numberly Moves from MongoDB to ScyllaDB to Simplify Operations and Reduce Costs

Numberly, a programmatic advertising firm, transitioned from MongoDB to ScyllaDB to simplify operations and reduce costs while maintaining data consistency and performance. Initially, Numberly faced challenges with MongoDB and Apache Hive due to the operational burden of maintaining two copies of ID matching tables and the inefficiencies in handling read/write latencies required by their service level agreements. The firm explored Apache Cassandra but found it unsuitable due to concerns with Java-related performance issues. After rigorous testing, ScyllaDB was chosen for its ability to handle workloads with low latencies and operational simplicity, allowing Numberly to replace a 15-node MongoDB cluster with a more efficient 3-node ScyllaDB cluster. This transition resulted in significant cost savings, improved data consistency, and enhanced performance, with Numberly's Chief Technology Officer praising ScyllaDB for its robust and smart open-source community.