DISQUS

Returning?

Login

Website
http://3.rdrail.net/blog
Original page
http://3.rdrail.net/blog/announcing-thruqueue-persistant-message-queue-for-thrudb/
Subscribe
All Comments
Community
Top Commenters
- Rod Page
  1 comment · 8 points
- seo company
  1 comment · 1 points
- Traveller_Adventure
  1 comment · 2 points
- ojbyrne
  2 comments · 1 points
- green cleaning seattle
  1 comment · 2 points
Popular Threads

Third Rail: Announcing Thruqueue: Persistant message queue for Thrudb

tobi · 1 year ago

Awesome. Unique Queues would be extremely useful in Shopify. How do they work? do they reject duplicates or remove existing entries and rather append the new one to the end of the queue?

Anyways, great addition but i'd almost wish this was a standalone product because it would also be supremely useful to legacy SQL apps.
jake · 1 year ago

It takes the MD5 of the message and maintains a hash of keys in the queue. It rejects the message (silently) if a message already exists in the queue at that time. I could also make it absolutely unique by maintaining a bloom filter on the queue, so no messages will ever be duplicated to the queue (overkill).

Thruqueue is a stand alone service. runs on its own port, etc.

Thrudb was built to be made up of separate services so people can pick and choose the services they want.
Jason · 1 year ago

Hooking it up to Spread would be great for redundancy and replication. Multiple servers, not one a master. Push and pull to each with message synchronization across the whole. Though ordering would have to be sacrificed or at the very least made an issue for the readers.