core VS API Platform

For instance, there are cache problems on Api Platform v3.0, so you should consider upgrading directly to the latest minor version available.

For a great setup to use as an example, see https://github.com/api-platform/core. The Behat library config is in behat.yml.dist, the feature files (process descriptions) are in the ./features directory, and the context files (Feature file Steps resolved to Context functions) can be found in ./tests/Behat.

/api/same-route is a unique identifier. Calling addPath with an existing identifier just overwrites your previous call, see https://github.com/api-platform/core/blob/main/src/OpenApi/Model/Paths.php You should call addPath once, and the instance of PathItem class should contain all HTTP methods, see constructor arguments.

We started in 2.5 and I believe I upgraded us to 2.6 just before leaving. What was with completely changing how OpenAPI generation worked in a minor release? That took a massive refactor for some of the special things were doing to hook in: https://github.com/api-platform/core/pull/3407 definitely a lot nicer to work with, but was painful for going up a minor version given our workload at the time.

Nope, not yep : https://github.com/api-platform/core/pull/1645

Technically API Platform is not part of Symfony. Although, they are both French. 😉

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.

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!

Just use a nice framework like Symfony and for an API there is a nice thing called API Platform

On the Symfony side, a headless API can be built really quickly with https://api-platform.com/. You describe your domain entities with Schema.org vocabulary, can use a client generator to hammer out a UI in Next, Nuxt, Quasar, or whatever as a starter, it comes with an admin backend, and a Helm chart to deploy on Kubernetes. Works great for APIs when paired with, say Nuxt SSGs/PWAs if you want more of a JAMstack approach.

It could be implemented with STOMP, or Mercure (goes well with API-Platform, written in PHP/Symfony), you could write your own with the help of nchan and scale it via Redis. If it's a web service, the best practices for operating and scaling are well established, Godot then just becomes another client.

Why would someone use this over API Platform?