Max Desiatov @maxd@mastodon.social
Public

@hongminhee洪 民憙 (Hong Minhee) this doesn't address serious concerns with GraphQL raised by the article I've linked. Both authorisation and rate limiting are crucial for client2server communication. You may achieve acceptable results using GraphQL with trivial well-behaved clients, in 2025 you can't assume every client is well-behaved. Bots will abuse the API no question, and without proper authorization and rate limiting it will bring servers down.

OpenAPI is much more flexible and doesn't have these issues.

just small circles 🕊 @smallcircles@social.coop
Public

@maxdMax Desiatov @hongminhee洪 民憙 (Hong Minhee)

What may be interesting is which is like but then oriented towards event-driven architectures. More appropriate for message passing protocols like .

asyncapi.com/en

AsyncAPI Initiative for event-driven APIs

Open source tools to easily build and maintain your event-driven architecture. All powered by the AsyncAPI specification, the industry standard for defining asynchronous APIs.

asyncapi.com

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/114505564217741823 on your instance and quote it. (Note that quoting is not supported in Mastodon.)