It sounds like you're trying to build a queue in Cassandra, which is one of the classic anti-pattern use cases for Cassandra.
You may be able to do something clever with triggers, but I highly recommend you look at purpose-built queuing software such as Kafka to solve this instead. On Tue, May 24, 2016 at 9:49 AM Aaditya Vadnere <sk1...@gmail.com> wrote: > Hi experts, > > We are evaluating Cassandra as messaging infrastructure for a project. > > In our workflow Cassandra database will be synchronized across two nodes, > a component will INSERT/UPDATE records on one node and another component > (who has registered for the specific table) on second node will get > notified of record change. > > The second component will then try to read the database to find out the > specific message. > > Is it possible for Cassandra to support such workflow? Basically, is there > a way for Cassandra to generate a notification anytime schema changes (so > we can set processes to listen for schema changes). As I understand, > polling the database periodically or database triggers might work but they > are costly operations. > > > -- > Aaditya Vadnere >
