2 ms·
GraphQL is trendy, but unless you need to maintain a lot of different versions of your API it doesn't really seem worth the investment.
by CuriouslyC 6y ago
GraphQL is trendy, but unless you need to maintain a lot of different versions of your API it doesn't really seem worth the investment.
- SkyPuncher 6y agoWe're exploring GraphQL because of the performance benefits of letting the client easily choose what it needs in the response data. The most prominent use case is lean list views and rich detail views. It's also helpful in views where related data is surfaced in detail. It can be done with REST, but there are enough edge cases that it's easier to simply follow a standard.