Hi All, @hanson
Can someone tell me if we have similar functionality of Oracle Advanced Queuing in SingleStore as well?
If not, what are the alternate ways?
Thanks
Himanshu
We don’t have similar functionality to Oracle Advanced Queuing. You can do something similar by creating queue tables in your database, with your application data. Then if you want to commit a change to a table and an associated queue message in a single transaction, you can do that like:
begin work
…
update db table
…
update queue table
…
commit
There are references out on the internet about how to implement a queue pattern with SQL and tables, e.g.
http://kejser.org/implementing-message-queues-in-relational-databases/
If you don’t care about being able to atomically update the database and a queue on a single transaction, you can use Kafka queues. See our documentation on Kafka pipelines, SELECT INTO Kafka, and so on.
And of course, if you want to use other queuing systems but don’t have an atomicity requirement, you could use them but you’d have to call the from external software, not from within the SingleStore database. An exception to that is you could write a SingleStore external function to call out to update a queue or get information from a queue. Again, that update would not be atomic with respects to the current SingleStore update transaction.