[zeromq-dev] ZeroMQ APIs for 2020

[Pieter Hintjens]

That page is old yet still accurate.

You can see a lot of this happening in CZMQ, which is becoming a
mainstream API for ZeroMQ. There are concepts like timers, pollers,
actors, smart sockets, which are much more profitable to use than
POSIX-style sockets.

My feeling (this is personal, and ZeroMQ tends to follow the group
mind more than any single opinion) is that "ZeroMQ is like sockets"
was a good selling point some years ago. Some of us (Sustrik) took
that as a literal goal, and it was a core mission of Nanomsg to
provide messaging via POSIX sockets. Others of us felt that API sucked
and built layers like CZMQ.

What we've seen in the meantime is that Nano has imploded, while the
CZMQ approach is rather popular. (Because it's fun to use, and lets
one work rapidly.)

-Pieter


On Sun, Feb 14, 2016 at 6:39 PM, Mario Steinhoff
<steinhoff.mario at gmail.com> wrote:
> Hi everyone,
>
> on http://zeromq.org/docs:features it says:
>
>> The ZeroMQ sockets have become models for well-defined packages of behavior. They even have their own RFCs full of SHALLs and MUST NOTs, like pub-sub and request-reply. The socket API and metaphor can only stretch so far before we feel "this was cool in 1980 but is kind of bizarre in 2020." There are better ways to make APIs. ZeroMQ has been repositioning itself towards those.
>
> What exactly is meant with that, e.g. what are those better ways and
> in how has ZMQ repositioned itself?
>
> Cheers
> Mario
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev