A Modern High-Performance Open Source Message Queuing System

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • blazingmq

    A modern high-performance open source message queuing system

  • Sounds great, and you have lots of nice documentation on the page, but could you provide a TLDR? There's a lot of competition in this area: GRPC, Cap'n'proto (was posted on HN a day or two ago), NATS, etc.

    I'm also having trouble figuring out if Mats3 is a library (with a JMS API) over a variety of messaging systems (WebSockets, NATS, etc.)?

    P.S. Some diagrams like https://bloomberg.github.io/blazingmq/ would be very helpful, especially at https://mats3.io/background/what-is-mats/. If a picture's worth a thousand words, and an animation must be worth at least 10k words. :)

  • mats3

    Mats3: Message-based Asynchronous Transactional Staged Stateless Services

  • I am truly finding it hard to explain it. I have tried along a dozen angles. I actually think it is a completely new concept - and that might be the problem.

    There is an illustration on the front-page: https://mats3.io/

    Here's a set of small answers to "What is Mats?": https://github.com/centiservice/mats3/blob/main/README.md#wh...

    Here's a way to code up Mats3 endpoints using JBang and a small toolkit which makes it extremely simple to explore the ideas: https://github.com/centiservice/mats3/blob/main/README.md#wh...

    If you read these and then get it, I would be extremely happy if you gave me a sentence or paragraph that would have led you to understanding faster!

    The use of JMS is just a transport. I could really have used anything, incl. any MQ, or ZeroMQ, or plain TCP - or just a shared table in a database.

    Wrt. WebSockets, that is a transport typically between a server, and a end-user client, e.g. an iOS App. Actually, there's also a "sister project", MatsSockets, that bring the utter async-ness of Mats3 all the way out to the client, e.g. a webpage or an app. https://matssocket.io/

    NATS is just a message queue, with some ability to orchestrate. I do not like this concept of orchestration as an external service, that is one of the founding ideas of Mats3: Do the orchestration within each service, as you would do if you employed REST as the ISC mechanism.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • BDE

    Basic Development Environment - a set of foundational C++ libraries used at Bloomberg.

  • Hi, one of the authors here. BlazingMQ depends on two other open source C++ libraries: https://github.com/bloomberg/bde and https://github.com/bloomberg/ntf-core. I believe documentation writer wanted to highlight that BlazingMQ does not depend on frameworks like ZooKeeper, etc.

  • ntf-core

    Sockets, timers, resolvers, events, reactors, proactors, and thread pools for asynchronous network programming

  • Hi, one of the authors here. BlazingMQ depends on two other open source C++ libraries: https://github.com/bloomberg/bde and https://github.com/bloomberg/ntf-core. I believe documentation writer wanted to highlight that BlazingMQ does not depend on frameworks like ZooKeeper, etc.

  • anime.js

    JavaScript animation engine

  • mosquitto

    Eclipse Mosquitto - An open source MQTT broker

  • I think he means implementation of MQTT protocol, like https://mosquitto.org/

  • norm

    NACK-Oriented Reliable Multicast (NORM) implementation & tools (RFCs 5740, 5401) (by USNavalResearchLaboratory)

  • NORM from the Naval Research Labs is another implementation of the same concept.

    https://github.com/USNavalResearchLaboratory/norm

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • OZ

    OpenMAMA/ZeroMQ bridge (by nyfix)

  • Unlikely, but they seem to be different things altogether. BlazingMQ appears to be a traditional message queue (think ActiveMQ), with message peristence. ZeroMQ is more of a network middleware (think Tibco Rendezvous), and does not include persistence.

    BlazingMQ also appears to be more of a "platform" or "service" that an app can use (sort of like Oracle, say) -- ZeroMQ includes libraries that one can use to build an app, service or platform, but none is provided "out of the box".

    Which makes it harder to get started with ZeroMQ, since by definition every ZeroMQ app is essentially built "from scratch".

    If you're interested in ZeroMQ, you may want to check out OZ (https://github.com/nyfix/OZ), which is a Rendezvous-like platform that uses the OpenMAMA API (https://github.com/finos/OpenMAMA) and ZeroMQ (https://github.com/zeromq/libzmq) transport to provide a full-featured network middleware implementation. OZ has been used in our shop since 2020 handling approx 50MM high-value messages per day on our global FIX network.

  • OpenMAMA

    OpenMAMA is an open source project that provides a high performance middleware agnostic messaging API that interfaces with a variety of proprietary and open source message oriented middleware systems. (by finos)

  • Unlikely, but they seem to be different things altogether. BlazingMQ appears to be a traditional message queue (think ActiveMQ), with message peristence. ZeroMQ is more of a network middleware (think Tibco Rendezvous), and does not include persistence.

    BlazingMQ also appears to be more of a "platform" or "service" that an app can use (sort of like Oracle, say) -- ZeroMQ includes libraries that one can use to build an app, service or platform, but none is provided "out of the box".

    Which makes it harder to get started with ZeroMQ, since by definition every ZeroMQ app is essentially built "from scratch".

    If you're interested in ZeroMQ, you may want to check out OZ (https://github.com/nyfix/OZ), which is a Rendezvous-like platform that uses the OpenMAMA API (https://github.com/finos/OpenMAMA) and ZeroMQ (https://github.com/zeromq/libzmq) transport to provide a full-featured network middleware implementation. OZ has been used in our shop since 2020 handling approx 50MM high-value messages per day on our global FIX network.

  • ZeroMQ

    ZeroMQ core engine in C++, implements ZMTP/3.1

  • Unlikely, but they seem to be different things altogether. BlazingMQ appears to be a traditional message queue (think ActiveMQ), with message peristence. ZeroMQ is more of a network middleware (think Tibco Rendezvous), and does not include persistence.

    BlazingMQ also appears to be more of a "platform" or "service" that an app can use (sort of like Oracle, say) -- ZeroMQ includes libraries that one can use to build an app, service or platform, but none is provided "out of the box".

    Which makes it harder to get started with ZeroMQ, since by definition every ZeroMQ app is essentially built "from scratch".

    If you're interested in ZeroMQ, you may want to check out OZ (https://github.com/nyfix/OZ), which is a Rendezvous-like platform that uses the OpenMAMA API (https://github.com/finos/OpenMAMA) and ZeroMQ (https://github.com/zeromq/libzmq) transport to provide a full-featured network middleware implementation. OZ has been used in our shop since 2020 handling approx 50MM high-value messages per day on our global FIX network.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts