ZeroMQ - A high-performance asynchronous messaging library that has been a game-changer for building distributed systems. Its simplicity and efficiency have made it a favorite tool in my toolkit for inter-process communication. I used it to implement a distributed event emitter for Node.js that I found useful in a couple of hobby projects. I find it to be much better than more popular tools (like Redis Pub/Sub or... - Source: dev.to / 7 months ago

The ImageProcessor in the repository has been implemented in C# using ZeroMQ and the NetMq nuget package. It also uses SixLabors.ImageSharp to resize the image. It consists of. - Source: dev.to / over 1 year ago

Open a new terminal connection and run the following commands (one after the other). The last command installs ZeroMQ. - Source: dev.to / almost 2 years ago

Interesting. They seem to warn against using the server for much as it's resource hungry and potentially unreliable, but that appears to be focused on the task of serving data; a simple webhook type use should be safer. It'd be pretty amazing if ESPHome supported something like ZeroMQ[0], so you could talk between nodes in anything up-to full-mesh at a socket-level and not need to worry about the availability of a... - Source: Hacker News / about 2 years ago

Https://zeromq.org/ -> TIL really cool, thanks for the pointer. - Source: Hacker News / about 2 years ago

When a team moves from a monolith into microservices and event-driven, asynchronous systems, it inherits a class of problems that used to be someone else's: work that fails halfway through, steps that must not run twice, calls that return before the work is done. Temporal is a durable execution engine that handles a lot of this - you define a multi-step process, and it guarantees the process runs to completion... - Source: dev.to / 16 days ago

Durable execution — the pattern implemented by Temporal, Inngest, Rivet Actors, and now Cloudflare Workflows — treats waiting as a continuation rather than a loop:. - Source: dev.to / 21 days ago

Two specific moves stand out in Duncan's account. The first is durable execution, via Temporal — Mercury replaced fragile cron-and-database state machines with workflow code whose failure semantics are platform-handled (replay, retry, timeout, cancellation). Mercury open-sourced its hs-temporal-sdk, which wraps Temporal's official Rust Core SDK via FFI and provides a Haskell-native API. The dovetail with Haskell's... - Source: dev.to / about 2 months ago

We picked Temporal as the first reference engine on purpose. Temporal has the strictest execution model we know of – a V8 sandbox, determinism constraints, replay-driven recovery. If our port contract holds up against that, easier engines – an in-memory test double, a BullMQ queue, or JSON-first platforms like Inngest or Restate – plug in through the same two interfaces. We're shipping Temporal first; the rest is... - Source: dev.to / 2 months ago

The trick is to find whatever metadata channel the queue already gives you and use that and thankfully, almost every mature queue has one (probably because of this scenario). SQS has message attributes, Temporal has context propagators built into the SDK, and Hatchet (which we use to run our workflows) has a metadata field called additionalMetadata. - Source: dev.to / 4 months ago