Thanks, I will take a look, but it looks abandoned. However, there might be some interesting stuff in there I can reuse.
Best regards On Sun, Jun 26, 2022 at 9:25 PM Arnaud Loonstra <[email protected]> wrote: > You could also have a look at https://github.com/zeromq/dafka > > On 26-06-2022 12:34, Nikola Radovanovic wrote: > > Thank you. > > I would like to make a custom-tailor message-broker, since it has to sit > > in between clients (console and web) with some load-balancing and LDAP > > backend. We already have some glimpse of it, but using cherrypy, which > > does not seem efficient enough. Also, for some pet-project I am working > > on, I would like to have something similar: REST-like service acting as > > a backend for javascript frontend. > > > > Kindest regards > > > > > > > > On Sat, Jun 25, 2022 at 10:08 PM Jim Melton <[email protected] > > <mailto:[email protected]>> wrote: > > > > Bear in mind that ZMQ is a message broker _toolkit_, not a > > full-fledged message broker. You can certainly implement these > > feature, but it isn’t supported out of the box. Unless your interest > > is in developing the middleware, you may want to look at a > > full-featured broker like Kafka, RabbitMQ or the like. > > -- > > Jim Melton > > > > > > > > > >> On Jun 24, 2022, at 2:56 AM, Nikola Radovanovic > >> <[email protected] <mailto:[email protected]>> wrote: > >> > >> Hi all, > >> a couple of questions, all related to a similar topic: I am > >> considering 0MQ as pub-sub message broker in an environment with a > >> small number of publishers and a large number of subscribers. > >> Publishers will be mainly processes like configure system, some > >> system events, etc. subscribers will be mainly web-clients but > >> also BASH console apps. > >> > >> 1. Now, what I am first interested in is message persistence. > >> Say, one node is publishing messages m1,m2,...mN. If something > >> happens to that node, I would like that non-published messages > >> are pulled from the DB and continue from that. Guess this is > >> not hard to achieve. > >> 2. Next, what about clustering: say want 2,3 or more nodes to > >> form a cluster and each one acts as proxy for all its > >> publishers/subscribers. Is there already a solution based on > >> 0MQ for this that is production ready? > >> 3. What is the recommended way to connect web clients? > >> > >> Many thanks > >> _______________________________________________ > >> zeromq-dev mailing list > >> [email protected] <mailto:[email protected]> > >> https://lists.zeromq.org/mailman/listinfo/zeromq-dev > >> <https://lists.zeromq.org/mailman/listinfo/zeromq-dev> > > > > _______________________________________________ > > zeromq-dev mailing list > > [email protected] <mailto:[email protected]> > > https://lists.zeromq.org/mailman/listinfo/zeromq-dev > > <https://lists.zeromq.org/mailman/listinfo/zeromq-dev> > > > > > > _______________________________________________ > > zeromq-dev mailing list > > [email protected] > > https://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ > zeromq-dev mailing list > [email protected] > https://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
