It's very confusing that they use the same name as the very well known PHP package manager, composer https://getcomposer.org/. - Source: Hacker News / 2 months ago

I'm embarrassed I never took the time to understand Composer until now. I have been preaching for a long time to start each PHP project with Composer, even when the project is not going end up on Packagist. - Source: dev.to / 2 months ago

Waaseyaa is a monorepo. The root composer.json defines 43 subpackages under packages/, each referenced as a path repository with @dev constraints. During development, this is convenient. Composer resolves everything locally, and you never think about versioning. - Source: dev.to / 4 months ago

(P)NPM is an outlier in this behavior compared to package managers of other languages. With package managers like Composer (PHP), pip (Python) and NuGet (.NET) dependencies are by default peer dependencies. That means that in those package managers it is not possible to have multiple versions of the same dependency in your application1. - Source: dev.to / 8 months ago

Download from getcomposer.org and follow installation instructions. - Source: dev.to / 10 months 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 / about 16 hours 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 / 6 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 1 month 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 / about 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 / 3 months ago