Get started on your path to becoming a ScyllaDB NoSQL database expert.
Take a Course
This paper looks at how teams can reduce that total cost of ownership by making 3 technical shifts.
This paper takes a closer look at those two major DynamoDB challenges, then presents a new approach to overcoming them – a technical shift with a simple migration path.
Read this paper to learn why and how 7 top gamechangers decided to modernize their database architecture with ScyllaDB, and what that move is enabling them to achieve.
Get key research findings from DZone’s study.
In this comparison we’ll show how ScyllaDB outperforms Aerospike — using Aerospike’s preferred test method.
This paper explains why and how Palo Alto Networks completely eliminated the MQ layer (Apache Kafka) and decided to use their existing low-latency distributed database (ScyllaDB) as an event data store and as a message queue.
Read this paper to learn how we configured a petabyte-scale benchmark, results with and without workload prioritization, tips and tricks that might benefit others planning their own petabyte-scale benchmark.
Learn why it is a mistake to assume that “p99” means that only 1% of users experience that set of latencies, and how p99 (and higher) outlier latencies can actually have a disproportionate effect on the system as a whole.
This paper outlines 7 key considerations that help teams tap the many benefits a DBaaS has to offer — without falling into some of the common traps.
An online travel booking company, Kiwi.com, experienced a worst-case scenario: a catastrophic fire in a datacenter running their customer-facing services. Learn how Kiwi survived, thanks to a well-planned high availability architecture, supported by the appropriate technologies.
This paper covers the tradeoffs between availability and consistency, the architectural differences between NoSQL and NewSQL plus see the YCSB benchmark results for ScyllaDB & CockroachDB.
When and how to migrate data from SQL to NoSQL are matters of much debate. It can certainly be a daunting task, but when your SQL systems hit architectural limits or your cloud provider expenses skyrocket, it’s probably time to consider a move.
Learn common approaches to caching data, seven reasons why external caching can be a bad choice, how ScyllaDB’s embedded cache isolates developers from cache-specific code and delivers greater reliability, better performance, and lower TCO, plus get real-world examples of successfully eliminating external cache by companies such as Comcast.
Many companies have migrated from DataStax Enterprise to ScyllaDB over the last few years. In doing so, these companies have realized faster, more consistent performance for their mission-critical applications, saved millions in infrastructure and licensing costs, and freed up countless hours previously spent tuning their systems in attempts to get desired levels of performance. Read to get a breakdown of ScyllaDB’s advantages
This guide covers best practices for maximizing the performance of ScyllaDB. Although ScyllaDB auto-tunes itself for optimal performance, users still need to apply best practices in order to get the most out of their ScyllaDB deployments.
ScyllaDB delivers the most scalable, fastest and most reliable NoSQL database as a managed service. This paper provides an overview of ScyllaDB Cloud and explains the underlying technology that makes ScyllaDB not only more performant than other DBaaS options but also much more cost-effective.
While scaling out the database is the norm for Big Data systems, there are many hidden costs and complexities associated with “node sprawl” that can be remedied by instead deploying smaller clusters of larger database nodes. This paper explores the merits of small clusters and shares test results that debunk the concerns some organizations have about using large nodes.
With a fundamentally different approach to architecting a database, ScyllaDB harnesses the ever-increasing computing power of modern infrastructure. Read this paper to learn about ScyllaDB’s deep architectural advancements.
ScyllaDB was architected and implemented by engineers with deep-level knowledge of operating systems and distributed systems, complemented by an appreciation for the power of control theory. A foundational architectural principle, self-optimizing capabilities manifest themselves in every aspect of the ScyllaDB database.
In this paper, we compare ScyllaDB with Amazon DynamoDB. We’ll cover the detailed methodology of our testing before demonstrating that ScyllaDB performs significantly better than Amazon DynamoDB under real-world conditions. Our evaluation also demonstrates that ScyllaDB delivers significant cost savings over Amazon DynamoDB.
Over-eager ingestion can result in a buildup of queues of background writes, possibly to the point of depleting available memory.This paper explains how ScyllaDB ensures that ingestion of data proceeds as quickly as possible, but not quicker.
Migration Guide: Apache Cassandra to ScyllaDB
ScyllaDB is a drop-in replacement for Apache Cassandra or Amazon DynamoDB. Transitioning from Cassandra to ScyllaDB is very straightforward. This guide covers the multi-step process of migrating the data and verifying its consistency.
2023 ©ScyllaDB | ScyllaDB, and ScyllaDB Cloud, are registered trademarks of ScyllaDB, Inc.
Apache® and Apache Cassandra® are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. Amazon DynamoDB® and Dynamo Accelerator® are trademarks of Amazon.com, Inc. No endorsements by The Apache Software Foundation or Amazon.com, Inc. are implied by the use of these marks.
