Im not seeing the "stream processing" piece here. Looks like they went from polling an RDBMS to some triggered querying of scylla, and then on to polling scyll

Im not seeing the "stream processing" piece here. Looks like they went from polling an RDBMS to some triggered querying of scylla, and then on to polling scylla. i.e. they went from polling an RDBMS to polling Scylla. They didnt replace kafka with anything so now their implementation isnt reactive. This is effectively no different that implementing a message queue in a database, with all the negatives that brings. They are sharding for each consumer to prevent multiple consumption due to lack of locks. What if a consumer goes down? How does it manage its own state? All things managed by kafka (or pretty much any MQ) out of the box, and now they have to implement ALL of that themselves - none of which is mentioned in the article.