Re:Kafka Removing Zookeeper Dependency
by StreamBright on Sunday May 17, 2020 @02:53PM
(#23214285)
I am familiar with Seastar too. It is one component that is pretty useless by itself. What is relevant in this topic is what is around it, the functionality that you provide. This is why Scylla is copying Cassandra. You can come up with a nice way of programming whatever you want but the end of the way the business functionality is what matters and there are different tradeoffs involved, still.
[ Parent
| on HN ]
Re:Kafka Removing Zookeeper Dependency
by manigandham on Sunday May 17, 2020 @05:30PM
(#23215656)
What do you mean "copying" Cassandra? Obviously they're offering the same API. Many people like the Cassandra data model and multiregional capabilities and that's why it was chosen.
What Scylla is doing is unlocking new performance potential with a C++ rewrite and an entirely different process-per-core architecture that gets around the fundamental limitations of Cassandra and makes it easier to run. This performance and stability has also led to the team making existing C* features like LWT, secondary indexes, and read-repair even faster and better than the original implementations.
While exposing a memory corruption friendly language into the internet.
What kinds of security assessments are done to guarantee that Scylla is as secure as Cassandra?
Re:Kafka Removing Zookeeper Dependency
by manigandham on Monday May 18, 2020 @06:01PM
(#23228901)
Sure, that's a valid but separate concern. You'd have to ask the dev team what their precise security approach is.