As word about Scylla continues to spread, we’re seeing more and more downloads of our open source software. We’re not always privy to our users’ experiences, but we’re very glad when we have the opportunity to share their results. A recent example of this is from Alexys Jacob of Numberly, who shared his experience evaluating Scylla for production on his personal Blog. In the first installment of a 2-part series, he describes his preparation for a successful POC-based evaluation with the help of the ScyllaDB team.
If you were forced to choose just one thing that would prompt you to move your mission-critical functionality to a new database, what would it be? Better performance? Worries about future scaling on your existing platform? Easier time for your DevOps? What about awesome support from the company itself? At Scylla Summit 2017, mParticle’s Nayden Kolev explained how all of the above factors started the group one year ago on a fruitful collaboration with Scylla in production.
They may not have time machines or lightsabers, but they do have the Higgs-Boson and they’re looking for the most scalable framework with which to study it. At CERN, the problem of the day is scaling out their AliEn global file catalog and their plans may well involve Scylla.
When an organization changes their database backend, it is not a simple task and there is usually an interesting story behind it. This was the case with Zenly, a mobile application that lets you know where your friends are in real time. They were using Elasticsearch as their main database to take advantage of its full-text search capabilities. However, Elasticsearch did not perform well for Zenly’s workload, which consists mostly of update operations, and they found it difficult to monitor and locate their data, so they began to look for a database replacement.
How do you quantify how effective your database system is in terms of throughput, latency and CPU usage? And what do you do when there is a risk to your SLA? These were the main questions explored in Lukasz Pachiarek and Szymon Szymanski of Allegro’s talk at Scylla Summit 2017.
Snapfish is an industry leader in photo retail with over 100 million members storing over 100PB of data. On a peak shopping day, Snapfish processes 100,000 reads and 7,000 writes per minute. Based on their workload, they need a database that accommodates their high volume but were increasingly finding that their database system was not meeting their performance and scaling needs. They began a search for alternatives and evaluated Scylla as a possible solution.
mParticle and ScyllaDB attended The NoSQL & NewSQL Database Meetup at the AWS Loft in NYC. Yuan Ren from mParticle gave a nice presentation that explained their journey from Apache Cassandra to Scylla and how they process 50 billion monthly messages with full availability and performance.
Guest post by By FengLin(MengYe Shen), Mogujie
Ori Lahav started a blog series about Scylla deployment at OutBrain You should check it out