GraphQL works great with a microservice architecture as well. In the end, GraphQL is just the API layer. It works great as kind of a thin API gateway that is responsible for routing the requests to the corresponding backend services.
Facebook is obviously not a monolith and that is what GraphQL was initially invented for.
I would just make sure to batch as much as possible and put those limits in place as mentioned in the article so you don't overwhelm your micro services.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
GraphQL works great with a microservice architecture as well. In the end, GraphQL is just the API layer. It works great as kind of a thin API gateway that is responsible for routing the requests to the corresponding backend services.
Here's a 30 minute video of Steven Luscher showing how to do that: youtube.com/watch?v=UBGzsb2UkeY
Facebook is obviously not a monolith and that is what GraphQL was initially invented for.
I would just make sure to batch as much as possible and put those limits in place as mentioned in the article so you don't overwhelm your micro services.