{"slug": "scylladb", "name": "ScyllaDB", "category": "databases", "category_name": "Databases", "description": "", "recommenders": 3, "commenters": 6, "warners": 0, "score": 3.241, "rising": 0.35, "first": "2025-11-03", "latest": "2026-08-07", "why": "(like this: https://www.scylladb.com/2021/04/06/scyllas-new-io-scheduler/)", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 2, "compare": 2, "warn": 0}, "spark": [0, 0, 1, 1, 0, 0, 0, 0, 0, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "(like this: https://www.scylladb.com/2021/04/06/scyllas-new-io-scheduler/)", "kind": "", "icon": true, "domain": "scylladb.com", "github_repo": null, "official_url": "https://www.scylladb.com/", "pricing": "", "aliases": ["ScyllaDB"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 787404321, "item_id": 49212770, "url": "https://news.ycombinator.com/item?id=49212770", "by": "rastignack", "date": "2026-08-07", "version": null, "stance": "recommend", "quote": "(like this: https://www.scylladb.com/2021/04/06/scyllas-new-io-scheduler/)", "excerpt": "I would be interested about a more detailed architecture overview of the io scheduler (like this: https://www.scylladb.com/2021/04/06/scyllas-new-io-scheduler/) and the thread scheduler. PostgreSQL has historically been bad at managing the noisy neighbor problem, but with thread pools, and io priorities, it can be solved. Has this been tackled here ?", "context": "", "use_case": "", "switched_from": "", "story": "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"}, {"id": 754659761, "item_id": 47166235, "url": "https://news.ycombinator.com/item?id=47166235", "by": "sgarland", "date": "2026-02-26", "version": null, "stance": "recommend", "quote": "Modulo places that have a clear need for something like Scylla", "excerpt": "IME, here are some signals that a company actually values correctness. This is not all-inclusive, nor is any one of them a guarantee. * Their codebase is written in something relatively obscure, like Elixir or Haskell. * They're an infrastructure [0] or monitoring provider. * They're running their code on VMs, and have a sane instantiation and deployment process. * They use Foreign Key Constraints in their RDBMS, and", "context": "", "use_case": "", "switched_from": "", "story": "Technical Excellence Is Not Enough"}, {"id": 748871008, "item_id": 46804438, "url": "https://news.ycombinator.com/item?id=46804438", "by": "em3s", "date": "2026-01-28", "version": null, "stance": "recommend", "quote": "ScyllaDB is a solid choice", "excerpt": "You might be right! ScyllaDB is a solid choice\u2014eventual consistency is often fine for interactions. The friction we hit was less about storage and more about fragmentation: teams kept rebuilding the same features (likes, views, follows) with slightly different implementations. Counters drifted, toggle logic varied, indexes duplicated. If you have one team and one use case, ScyllaDB could work well. Our problem was mu", "context": "", "use_case": "Wide-column database", "switched_from": "", "story": "Show HN: Actionbase \u2013 A database for likes, views, follows at 1M+ req/min"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["wide-column database"], "compared": [{"slug": "postgresql", "name": "PostgreSQL", "co": 4, "switched_from": 0, "switched_to": 0}, {"slug": "kubernetes", "name": "Kubernetes", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "redis", "name": "Redis", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "clickhouse", "name": "ClickHouse", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "mysql", "name": "MySQL", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "elasticsearch", "name": "Elasticsearch", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "vue-js", "name": "Vue.js", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "datadog", "name": "Datadog", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49208535", "title": "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47741527", "title": "Ask HN: What Are You Working On? (April 2026)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47601859", "title": "Ask HN: Who is hiring? (April 2026)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47163985", "title": "Technical Excellence Is Not Enough", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46778273", "title": "Show HN: Actionbase \u2013 A database for likes, views, follows at 1M+ req/min", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=45934940", "title": "I can't recommend Grafana anymore", "mentions": 1}], "sentiment_by_month": {"2025-11": {"neutral": 1, "compare": 1}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {"recommend": 1}, "2026-03": {}, "2026-04": {"neutral": 1, "compare": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"recommend": 1}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 787404321, "item_id": 49212770, "url": "https://news.ycombinator.com/item?id=49212770", "by": "rastignack", "date": "2026-08-07", "version": null, "stance": "recommend", "quote": "(like this: https://www.scylladb.com/2021/04/06/scyllas-new-io-scheduler/)", "excerpt": "I would be interested about a more detailed architecture overview of the io scheduler (like this: https://www.scylladb.com/2021/04/06/scyllas-new-io-scheduler/) and the thread scheduler. PostgreSQL has historically been bad at managing the noisy neighbor problem, but with thread pools, and io priorities, it can be solved. Has this been tackled here ?", "context": "", "use_case": "", "switched_from": "", "story": "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"}, {"id": 764009923, "item_id": 47750620, "url": "https://news.ycombinator.com/item?id=47750620", "by": "dwighson", "date": "2026-04-13", "version": null, "stance": "compare", "quote": "ScyllaDB on the same hardware does 49K.", "excerpt": "Building Warp (https://warp.thegeeksquad.io), a storage engine where each entity is its own actor with its own SQLite shard. I've been doing DDD and event sourcing for years but always had to squeeze aggregates and domain events into Postgres tables. I kept looking at what scaling would mean with CockroachDB or ScyllaDB and it scared me. So I asked what happens if you just make SQLite the storage and let the BEAM han", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: What Are You Working On? (April 2026)"}, {"id": 761630114, "item_id": 47601882, "url": "https://news.ycombinator.com/item?id=47601882", "by": "Tina-Fet", "date": "2026-04-01", "version": null, "stance": "neutral", "quote": "ScyllaDB, Redis, ElasticSearch", "excerpt": "Head of Engineering & Infrastructure | Full-Time | Remote | $182k - $272k USD - https://fetlife.com/jobs/head_of_engineering_and_infrastructure Role: Fully own our engineering and infrastructure teams, keep FetLife fast and reliable for over 12 million members, and free the rest of the leadership team to focus on product and growth. How to Apply: Email jointheteam+hoei+hn@fetlife.com with a brief introduction, tell u", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: Who is hiring? (April 2026)"}, {"id": 754659761, "item_id": 47166235, "url": "https://news.ycombinator.com/item?id=47166235", "by": "sgarland", "date": "2026-02-26", "version": null, "stance": "recommend", "quote": "Modulo places that have a clear need for something like Scylla", "excerpt": "IME, here are some signals that a company actually values correctness. This is not all-inclusive, nor is any one of them a guarantee. * Their codebase is written in something relatively obscure, like Elixir or Haskell. * They're an infrastructure [0] or monitoring provider. * They're running their code on VMs, and have a sane instantiation and deployment process. * They use Foreign Key Constraints in their RDBMS, and", "context": "", "use_case": "", "switched_from": "", "story": "Technical Excellence Is Not Enough"}, {"id": 748871008, "item_id": 46804438, "url": "https://news.ycombinator.com/item?id=46804438", "by": "em3s", "date": "2026-01-28", "version": null, "stance": "recommend", "quote": "ScyllaDB is a solid choice", "excerpt": "You might be right! ScyllaDB is a solid choice\u2014eventual consistency is often fine for interactions. The friction we hit was less about storage and more about fragmentation: teams kept rebuilding the same features (likes, views, follows) with slightly different implementations. Counters drifted, toggle logic varied, indexes duplicated. If you have one team and one use case, ScyllaDB could work well. Our problem was mu", "context": "", "use_case": "Wide-column database", "switched_from": "", "story": "Show HN: Actionbase \u2013 A database for likes, views, follows at 1M+ req/min"}, {"id": 734981747, "item_id": 45936359, "url": "https://news.ycombinator.com/item?id=45936359", "by": "pas", "date": "2025-11-15", "version": null, "stance": "compare", "quote": "if there's need for scaling out it'll look like Cassandra, Aerospike, ScyllaDB, or ClickHouse", "excerpt": "logs, spans and metrics are stored as time-stamped stuff. sure simple fixed-width columnar storage is faster, and makes sense to special case for numbers (add downsampling and aggregations, and histogram maintenance and whatnot), but any write-optimized storage engine can handle this, it's not the hard part (basically LevelDB, and if there's need for scaling out it'll look like Cassandra, Aerospike, ScyllaDB, or Clic", "context": "", "use_case": "", "switched_from": "", "story": "I can't recommend Grafana anymore"}, {"id": 732807618, "item_id": 45800476, "url": "https://news.ycombinator.com/item?id=45800476", "by": "Tina-Fet", "date": "2025-11-03", "version": null, "stance": "neutral", "quote": "ScyllaDB", "excerpt": "FetLife | Senior DevOps Engineer | Full-Time | Remote | 115k - 180k USD - https://fetlife.com/jobs/devops-engineer Role: Develop and implement infrastructure upgrades, database tuning, Kubernetes and Helm orchestration, monitoring, and security. Help maintain and improve our large-scale Rails monolith, including CI/CD. Participate in on-call rotation and help automate daily DevOps tasks. Stack: MySQL/PostgreSQL, Scyl", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: Who is hiring? (November 2025)"}]}