Scylla came out on top and is now in production at Grab. In this post, you can learn more about Grab’s journey to Scylla and see what they liked about it.
In the context of graph databases, the performance of your storage backend is paramount. In the world of edges and vertices, graphs (and the data required to support them) can grow exponentially in a point-to-point fashion. In their talk at Scylla Summit 2017, Ted Chang and Chin Huang, both engineers at IBM, decided to add Scylla to the mix of backends which has traditionally included Cassandra and HBase. They ran test scenarios which covered high volume reads and writes, and provided comparative test results for the three backends, along with lessons learned for each.
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.
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.
At ScyllaDB, our development team is all about performance with improved latency and throughput. Our speakers at our recent Scylla Summit provided many tips and tricks to make Scylla’s superior latency and performance even better. ScyllaDB’s VP of R&D, Schlomi Livne, added to the growing repertoire of these tips with his talk Planning your queries for maximum performance. In it, he outlined some of the how and why of Scylla performance, and concluded with seven rules to optimize your queries.
Apache Cassandra may have served you well. But alas, nothing is ever perfect, so you’re looking to migrate. Typically sub-millisecond consistency, performance of various operations, compaction, as well as read/write latency (especially under heavy loads) can be less than optimal.
In previous documentation installments, you’ve learned about Scylla’s ring architecture and you’ve dug into our fault tolerance documentation. Ready to get your hands dirty? Our consistency level console demo can help you get started immediately.
ScyllaDB is all about performance, so it’s no surprise that this was the theme of day two at our Scylla Summit.
What happens if a catastrophe occurs in or between your data centers? What if a node goes down or becomes unreachable for any reason? Scylla’s fault tolerance features significantly mitigate the potential for catastrophe. To get the best fault tolerance out of Scylla, you must understand how to select the right fault tolerance strategy, which includes setting a Replication Factor (the number of nodes that contain a copy of the data) for your keyspaces and choosing the right Consistency Level (the number of nodes that must respond to read or write operations). We recently added new documentation to our Scylla […]