This is unfair. I made Mats so that I could use messaging in a simpler form. Nothing else. Mats is an API that can be implemented on top of any queue-based mes

This is unfair. I made Mats so that I could use messaging in a simpler form. Nothing else. Mats is an API that can be implemented on top of any queue-based message broker - which excludes Kafka. But it definitely includes ApacheMQ (which is what we use), Artemis and hence RedHat's MQ (which the tests runs), and RabbitMQ (whose JMS implementation is too limited to directly be used, but I do hope to implement Mats on top of it at some point). Probably also NATS. Probably also Apache Pulsar, which I just recently realized have a JMS client. You could even implement it on top of ZeroMQ, and implement it on top of any database, particularly Postgres since it has those "queue extensions" NOTIFY and SKIP LOCKED. edit: I actually have an feature-issue exploring such an implementation: https://github.com/centiservice/mats3/issues/15 https://github.com/centiservice/mats3/issues/15