3 ms·
Honestly, prefer GraphQL -- it's more like designing a schema which you may already be doing in your database anyway. The client decides which data in what shap
by mattbillenstein 6y ago
Honestly, prefer GraphQL -- it's more like designing a schema which you may already be doing in your database anyway. The client decides which data in what shape it fetches.
- dehrmann 6y agoIf you're designing an internal API to power a rich client app, yes. If you're designing an API for developers to interface with you SaaS, plain old HTTP is a better choice, even if it's only RESTful in a hand wavy sense.
- mattbillenstein 6y agoYeah, agree - if your product is an api, I'd have REST first, then graphql later perhaps if people are interested in that.