laconia
laconia copied to clipboard
How might we abstract GraphQL?
Is your feature request related to a problem? Please describe.
GraphQL is a new trend for Microservice API Architecture. At the same time, I'm also reluctant to introduce an unnecessary abstraction. Is there a middle ground that covers 80% of user's use cases? How will the API look like if we want to help developers use GraphQL?