Another difference is that in .NET Core, we can integrate with OpenAPI out of the box (it is part of the framework), while in Symfony, an API-based application with OpenAPI features is only available using a third-party tool—the API Platform. - Source: dev.to / about 2 years ago

API Platform is a great tool for rapid API development, but it has a lot of not-so-well-documented features which can sometimes lead to confusion. Playing around with a new project of mine I've stumbled into one: tests were failing for my validation assertions of endpoints' responses! - Source: dev.to / about 2 years ago

Technically API Platform is not part of Symfony. Although, they are both French. 😉. - Source: dev.to / over 2 years ago

Probably API-platform. The website is down at the moment, but: https://github.com/api-platform/api-platform It's Symfony based (and plays nice in that ecosystem), also allows you to describe entities via Schema org vocab, has a client generator, and comes with docker-compose and helm charts. I've used it extensively to build various headless services. It's really easy to expose annotated Doctrine entities. Source: about 3 years ago

API Platform is a framework for API-first projects, built on top of Symfony components. Let's see how to create a minimal and lightweight starter project in just 5 minutes! - Source: dev.to / about 3 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 / 5 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 / 11 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 / 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