Registrator VS GraphQL

Had the same problem recently, and was close to building a tool like yours. But I discovered Registrator. I added a small Consul instance and the consul provider configuration to traefik. Registrator ( https://github.com/gliderlabs/registrator ) automatically registers new docker services on the second maschine. Stopped services are automatically unregistered. Had to cross build Registrator for arm64, but this... Source: about 1 year ago

On the other hand, GraphQL is a query language for APIs that was developed by Facebook. It allows clients to specify exactly what data they need, and the server responds with only that data. - Source: dev.to / 5 days ago

In this article, I’ll show why GraphQL is the preferred approach over a RESTful API here, demonstrating how to deploy Apollo Server (and Apollo Explorer) to get up and running quickly with GraphQL. - Source: dev.to / 11 days ago

GraphQL is a query language and runtime for APIs. It provides a flexible and efficient way for clients to request and retrieve specific data from a server using a single API endpoint. - Source: dev.to / about 1 month ago

When you use technologies like GraphQL, it is trivial to derive TypeScript types. A GraphQL API is created by implementing a schema. Generating the TypeScript type definitions from this schema is simple, and you do not have to do any more work than just making the GraphQL API. This is one reason why I like GraphQL so much. - Source: dev.to / about 2 months ago

REST and GraphQL have advantages, drawbacks, and use cases for different environments. REST is for simple logic and a more structured architecture, while GraphQL is for a more tailored response and flexible request. - Source: dev.to / about 2 months ago