4 ms·
Whenever you see REST in the article, think RPC. The author even says REST is simpler than GraphQL but I suspect they hadn’t implemented a REST API… ever.
by nesarkvechnep 2y ago
Whenever you see REST in the article, think RPC. The author even says REST is simpler than GraphQL but I suspect they hadn’t implemented a REST API… ever.
- 9dev 2y agoWhat is that you find so complex about RESTful APIs?
- k__ 2y agoI assume, it's less about the complexity and more about most people not understanding REST.
- DanielHB 2y agoPure REST API is a huge pain in the ass to use and leads to bad performance because of waterfall requests. It is like the number one thing GraphQL solves for most people, decide which nested relationships to inline into a response. The simplicity makes it bad to use, if you work around the simplicity (arbitrary inlining, extra fields to choose what to inline, etc) then you end up with non-standard complexity.
- nesarkvechnep 2y agoBad performance if you haven’t heard about HTTP caching. REST implies cacheabality.
- baq 2y agoI’ve done it once in my two decades of being paid to code and only because it was small enough to not impact any timelines… nobody cared anyway. Otherwise REST now means ‘RPC over HTTP with JSON marshaling’ for better or worse.