Free audit

View Audit Scope
ScyllaDBRemote DBA, support, and scoped projects

ScyllaDB database services for production teams.

JusDB provides ScyllaDB database services for scoped projects, ongoing remote DBA coverage, production support, performance tuning, upgrades, and migrations from Cassandra or DynamoDB. We work on your own servers and cloud VMs, on Kubernetes with the ScyllaDB Operator, and with ScyllaDB Cloud. 24x7 on-call is available under your service agreement.

Or request a free audit of one database instance. Already in an incident? See how incidents are handled.

  • NDA before access
  • Read-only by default
  • Changes measured against your baseline

ScyllaDB version status

Pick the version you run

ScyllaDB 2026.3

Newest release

A feature release, generally available since September 2026, and supported until 2027.1 ships.

From 2026.2, vnode keyspaces can move to tablets online, within limits such as a single datacenter and Incremental Compaction Strategy tables.

Plan the move to tablets

Version status from the ScyllaDB version support page, the upgrade policy, and the source-available license FAQ, checked 28 October 2026.

Platforms
Your own servers, cloud VMs, Kubernetes with the ScyllaDB Operator, and ScyllaDB Cloud
High availability
Racks and datacenters with NetworkTopologyStrategy, LOCAL_QUORUM, Raft for schema and topology, and scheduled repair
Incidents
Initial-response targets are set in your service agreement. See the targets

Symptoms

Eight ScyllaDB problems we are asked to fix

Each one has a cause we can measure. The scoping call starts from the symptom you see and the version and platform you run.

  1. One CPU core runs at its limit while the rest sit idle because one partition key takes most of the requests, and each partition is served by one shard on each replica.

  2. Deleted rows come back after a node outage because the table uses tombstone_gc timeout mode, and no repair covered it within gc_grace_seconds (10 days by default).

  3. One partition grows without bound because its key has no time bucket, and by default ScyllaDB warns only once a partition passes 1,000 MB or 100,000 rows.

  4. A datacenter goes down and node replacement stops because a cluster with two equal datacenters loses its Raft majority, which schema and topology changes need.

  5. Disks run short during compaction because size-tiered compaction (STCS) can need up to half the disk free, where Incremental Compaction Strategy (ICS) needs far less.

  6. A change data capture (CDC) consumer misses changes after falling behind, because rows in the CDC log table expire after 24 hours by default.

  7. The upgrade off Open Source 6.2 keeps slipping because 6.2 was the last AGPL release, and later releases are free only within 50 vCPUs and 10 TB of storage per organization.

  8. DynamoDB calls fail after a move to Alternator because Alternator does not implement multi-item transactions such as TransactWriteItems, PartiQL, or the DynamoDB backup APIs.

If one of these is costing your team time, a scoping call is the place to start.

Book a 30-min scoping call (opens Google Calendar in a new tab)

Hot shard

How one hot partition stalls a ScyllaDB shard

ScyllaDB splits each node into shards, one per CPU core, and each partition is served by one shard on each replica. When one key takes most requests, its shard saturates while the others idle, and more nodes do not split it.

One node, three of its shards, three outcomes

Choose a state to see where the requests land.

Application and routing

A shard-aware driver sends each request straight to the shard that owns its partition.

Load spread across shards
  • Shard 0

    Many partitions, none dominant

    Busy, not saturated

  • Shard 1

    Many partitions, none dominant

    Busy, not saturated

  • Shard 2

    Many partitions, none dominant

    Busy, not saturated

Requests spread over many partitions, so each core carries a similar share of the work.

We alert when one shard runs far busier than the others, then find the key behind it with nodetool toppartitions. We redesign that key with your developers, adding a bucket where one key can take a large share of traffic.

For a key that can still spike, we set per_partition_rate_limit (max_reads_per_second and max_writes_per_second), so ScyllaDB rejects part of the excess to reduce the overload. It is protection, not an exact cap: the accepted rate can be up to the replication factor times the limit. We rehearse each change on a copy.

What we cover

Full-spectrum ScyllaDB engineering

From a saturated core to an upgrade off 6.2: nodetool, ScyllaDB Monitoring Stack, and repair history drive every change.

  • Cluster architecture

    Clusters laid out for your data, failure domains, and growth.

    • Tablets or vnodes chosen when each keyspace is created
    • Replication factor and racks set per datacenter
    • A third datacenter, which can be one zero-token node, to keep a Raft majority
    ScyllaDB consulting
  • Performance tuning

    Latency traced to the shard, partition, or compaction behind it, and measured against your baseline.

    • Hot partitions found with nodetool toppartitions
    • A compaction strategy matched to each table's writes
    • Workload prioritization, with more shares for live traffic than analytics
    Database performance tuning
  • Migration from Cassandra

    Moves from Apache Cassandra over CQL, with a tested way back (a rollback plan).

    • CQL schema and driver compatibility checked first
    • Dual writes, then a bulk load with ScyllaDB Migrator
    • Row counts and sampled reads compared before cutover
    Cassandra vs ScyllaDB
  • Alternator setup

    The DynamoDB-compatible API (Alternator) set up for the calls your application makes.

    • A write isolation policy per table, from always_use_lwt to forbid_rmw
    • Load balancing in front of the nodes
    • Unimplemented calls, such as TransactWriteItems, found before cutover
    DynamoDB services
  • High availability

    Replication and repair designed around the data loss and downtime you can accept (RPO and RTO), then drilled.

    • Racks and datacenters laid out so one failure leaves a quorum
    • Repair scheduled with ScyllaDB Manager, or automatic repair on tablets
    • tombstone_gc repair mode, which drops a delete marker only after repair
    Database high availability
  • Managed operations

    Backups, monitoring, and upgrades under an agreed scope, with restores tested on a copy.

    • Backups to Amazon S3 or Google Cloud Storage with ScyllaDB Manager
    • ScyllaDB Monitoring Stack dashboards and alerts
    • Rolling upgrades, one node at a time
    Backup and disaster recovery

Incident support

A critical (P1) page, answered within your agreement's target

JusDB keeps your recovery procedures (runbooks) written down, so an incident starts from a known plan instead of a blank page.

Initial-response targets

  • 2 to 4 hours

    Business hours

    During covered business hours

  • 15 minutes

    24x7 on-call

    P1 incidents

P1 · Critical15 minutes

Production database down, primary unreachable, data corruption risk, or active failover event.

P2 · High30 minutes

Severe latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.

P3 · Medium60 minutes

Non-critical slow query regression, staging issue, backup warning, or replication check alert.

P4 · Low90 minutes

Configuration question, index advisory, planned schema review, or general operational request.

Our engineering team is in India; business-hours coverage is Mon–Fri 09:00–18:00 IST (UTC+5:30), and 24x7 on-call is available under your service agreement.

Initial-response targets, not resolution guarantees. The target for your engagement is set in your service agreement.

What happens on a P1 page

  1. Page

    You page the on-call engineer

    Through the escalation path your service agreement names.

  2. Triage

    Root cause from per-shard metrics, logs, and tracing

    Saturated shards, compaction backlogs, repair gaps, and timeouts traced to the table and partition behind them.

  3. Mitigate

    Stabilize first, from the runbook

    Shed load on a hot partition with a per-partition rate limit, throttle compaction, pause scheduled repairs, or stop CQL traffic to a struggling node with nodetool disablebinary, then fix the cause.

  4. After

    A review after every P1

    What happened, why, and the change that stops it happening again.

Before and between incidents

  • Your setup, written down firstDuring onboarding we record your versions, datacenters, racks, replication factors, and repair and backup schedules, so an incident starts with context.
  • One escalation path, in writingYour service agreement names how to reach the on-call engineer and in which hours.
  • Reviews between incidentsWe review shard balance, large partitions, compaction, repair coverage, free disk, and backups, and report open risks with next steps.
  • Version dates trackedWe track ScyllaDB support dates and license limits for the releases you run, and plan upgrades before support ends.

Process

How a ScyllaDB engagement runs, step by step

Written findings come before any change. Your team approves production changes, except routine actions you have pre-approved.

  1. Scoping call

    Your clusters, versions, datacenters, platforms, and what you need covered.

  2. Read-only review under NDA

    Our engineers use named accounts with only the permissions the review needs, then read your schema, scylla.yaml, nodetool output, ScyllaDB Monitoring Stack dashboards, logs, and ScyllaDB Manager history.

  3. A written report before any change

    Each finding comes with the change we propose, how we will measure it, and a way to undo it (a rollback plan).

  4. Changes, then handover

    We rehearse risky changes on a copy, apply them in windows you approve, measure them against the baseline, and update the operating instructions (runbooks).

Ways to work

Choose the ScyllaDB service your team needs

Start with the responsibility you need covered. Each engagement has its own scope, deliverables, access requirements, and acceptance criteria.

Where your ScyllaDB runs, and the tools around it

Your team and ours

What a managed ScyllaDB service still leaves to your team

Managed cloud databases automate much of the infrastructure layer, but your team still owns query performance, capacity, cost, and incident decisions.

Who handles each part of running ScyllaDB on a managed cloud service and on your own servers
QuestionManaged cloud serviceYour own servers or Kubernetes
Servers, storage, and patchesThe provider runs them.Your team, or JusDB under your agreement.
Backups and restoresBuilt in on ScyllaDB Cloud: a full backup daily, kept for 14 days by default. You still test a restore.Your team runs ScyllaDB Manager backups to object storage and tests the restores.
Data model, partitions, and queriesYours. The provider runs the platform, not your tables or queries.Yours.
Where the data runsIn the provider's cloud account, or in your own AWS or Google Cloud account with the bring-your-own-account option.On servers, VMs, or Kubernetes nodes you run.
Moving off laterOver CQL or Alternator, read by a migration tool you run.Backups, snapshots, or a read over CQL move the data elsewhere.

Your team keeps control

  • Set business priorities, application requirements, and release plans
  • Approve production changes, except routine actions you have pre-approved
  • Own your cloud accounts, access policies, and vendor relationships
  • Decide when maintenance can happen and how quickly service must recover
  • Move the work in-house or to another provider after your agreement's notice period, with your data returned or deleted and the transition help your agreement sets out (Terms, section 8)

JusDB handles the agreed database work

  • Monitor database health, investigate alerts, and involve the right people
  • Review query performance, replication, capacity, and backup health
  • Carry out approved changes and update the operating instructions they affect
  • Report completed work, open risks, and recommended next steps

Weighing ScyllaDB Cloud against running ScyllaDB yourself? We compare both against your workload on a scoping call.

Book a 30-min scoping call (opens Google Calendar in a new tab)

Further reading

Two modeling guides and a comparison

Guides to designing CQL and DynamoDB tables from your queries, and a comparison with Apache Cassandra.

FAQ

Common ScyllaDB questions

What buyers ask about Cassandra, DynamoDB, performance, security, and monitoring.

Still have a question?

Ask it on a scoping call. No production access needed.

Book a 30-min scoping call (opens Google Calendar in a new tab)

How does ScyllaDB compare to Apache Cassandra?

JusDB treats ScyllaDB as a Cassandra-compatible engine. It speaks CQL and works with Cassandra drivers. It is written in C++ and runs one shard per CPU core, with no Java virtual machine (JVM) and no garbage-collection pauses. Tuning moves to shard balance, compaction, and repair.

What is the migration path from Cassandra to ScyllaDB?

JusDB first checks your schema and drivers against ScyllaDB's CQL support. Then we start dual writes from the application, bulk-load existing data with ScyllaDB Migrator, and compare both clusters before cutover. We rehearse the cutover on a copy, with a written rollback plan. JusDB does not guarantee one cutover duration.

Can ScyllaDB replace DynamoDB using Alternator?

JusDB answers per application: Alternator, ScyllaDB's DynamoDB-compatible API, covers most of the API, not all of it. It lacks multi-item transactions (TransactWriteItems and TransactGetItems), PartiQL, and the backup and point-in-time restore APIs, and it ignores provisioned throughput. We check each call your application makes before cutover.

What is ScyllaDB's performance advantage?

JusDB explains it as a design, not a promised number. ScyllaDB is written in C++ on the Seastar framework, and each CPU core gets its own shard, memory, and scheduler. That avoids JVM garbage-collection pauses and most locking between cores. We measure the gain on a copy of your workload.

How do you handle ScyllaDB security?

JusDB first turns on authentication and authorization, because the defaults, AllowAllAuthenticator and AllowAllAuthorizer, perform no checks. We then set least-privilege roles, encryption in transit (TLS) and at rest, and audit logging. Alternator does not enforce authorization by default either, so we turn on alternator_enforce_authorization. These controls can support your compliance programs, but do not certify compliance.

What monitoring do you provide for ScyllaDB?

JusDB sets up ScyllaDB Monitoring Stack (Prometheus, Grafana, and Alertmanager), with alerts on latency, shard balance, compaction backlog, repair age, free disk, and failed backups. Each critical (P1) incident ends with a written review. Initial-response targets are 2 to 4 hours during covered business hours, Mon–Fri 09:00–18:00 IST (UTC+5:30). Where your service agreement includes 24x7 on-call, the initial-response target for P1 incidents is 15 minutes. Targets are not resolution guarantees.

Next step

Talk to a ScyllaDB engineer about your databases

Tell us what is slow, fragile, or due to change. The first 30-minute call covers your databases, current ownership, and required coverage. No production access is needed. Or request a free audit of one database instance, subject to availability: mutual NDA before read-only access, a prioritized report within one week after access is ready, and no obligation.

NDA before access, read-only by default, and written scope first