11 engineers on Hacker News describe using ScyllaDB first-hand: 6 endorse it, 2 regret it, 1 are mixed.
“I like Scylla and we use it, so I wish them well. But what I don't understand with this announcement is how it supposed to work if they don't publish the pricing model.”
mixed · production · splix · 2024-12-18 · source ↗ · wrong label?“Where I work we tried to use it in workload with high read and writes and it had trouble to keep up.”
regret · production · nzach · 2023-10-05 · source ↗ · wrong label?“switched from Cockroach ... to Yugabyte en Scylla recently ... this works very well for us.”
endorse · production · tluyben2 · 2022-10-20 · source ↗ · wrong label?“We moved to it from Cassandra and have had no stability issues at all. Our use case is several 100k requests per second”
endorse · production · secondcoming · 2021-03-22 · source ↗ · wrong label?“We switched to Scylla a year or so ago, haven't looked back.”
endorse · production · 1 yr · secondcoming · 2020-11-24 · source ↗ · wrong label?“we switched from Cassandra (JVM) to Scylla (C++). It was a win in terms of both query latency and infrastructure costs”
endorse · production · dirtydroog · 2020-05-24 · source ↗ · wrong label?“we switched from Cassandra (JVM) to Scylla (C++). It was a win in terms of both query latency and infrastructure costs”
endorse · production · _ph_ · 2020-05-24 · source ↗ · wrong label?“we decided to use ScyllaDB instead and worry about more important things.”
endorse · production · manigandham · 2018-09-21 · source ↗ · wrong label?“we did use or test MongoDB, Cassandra (including ScyllaDB), HBase”
regret · personal · doh · 2017-10-05 · source ↗ · wrong label?“it was cassandra at the time of rewrite, scylla now since we've migrated our data stores over”
neutral · production · jhgg · 2021-02-22 · source ↗ · wrong label?“For that we run ScyllaDB.”
neutral · production · manigandham · 2018-11-28 · source ↗ · wrong label?