3 ms·
For starters: - Use a better a GC like Azul's C4. - Leverage monitoring to shard off hot spots. - If possible, get away from CPU- & memory-inefficient JVM an
by 1letterunixname 4y ago
For starters:
- Use a better a GC like Azul's C4.
- Leverage monitoring to shard off hot spots.
- If possible, get away from CPU- & memory-inefficient JVM and dynamic languages.
- Steer clear from ScyllaDB and its radioactive license. And, there's little customer demand for it. Astra DB for a commercial distro or YugabyteDB is from the folks behind Cassandra.
- Optimize persistence with multiple choices of backends that abstract away the underlying datastore: the eases the pain of going through "divorce" from any particular technical solution. Writes vs. Reads ratios, geographic replication, object size, data structure (K/V, tuplestore, time series, files, etc.)
- thekozmo 4y agoScyllaDB uses AGPL, a good and valid license
- fruit2020 4y agoWhat’s the deal with scylla? Everytime I google something cassandra related I get only scylla ads claiming it’s much better
- secondcoming 4y agoIt's a more performant equivalent. When we switched to it we reduced the number of nodes required and query latencies were better.