API Digest #55: RPC vs REST Is or Is Not in the URL?
Hi, dear readers! As promised two weeks ago, we are back with more reading material. In this API Digest, we are overviewing the following topics:
- Swagger Ain't Rest - Is That Ok?
- Understanding REST And RPC For HTTP APIs
- RPC vs. REST is not in the URL
- Caching for faster APIs
- How to build an evolvable distributed system
- What to do when Chrome drops support for your REST API testing
- API SDKs are getting more specialized
- Architecting Real-time Bulk Async APIs
With the care that fewer API strategies end up being hamstrung by a faith-like allegiance to an incorrect understanding of REST, Howard Dierking briefly waded into the general topic of the architectural style. Read Swagger Ain't Rest - Is That Ok? to not only comprehend what REST is, but also figure out if it fits for what you are trying to do.
HTTP caching mechanisms can improve the performance of APIs, and not taking advantage of them is a lost opportunity, believes Lori MacVittie. To learn more on this topic, read Caching for Faster APIs.
Once pulled into a discussion about the effect of contracts in distributed systems and having too many ideas to make them into 140 characters, Oliver Gierke wrote an article that the majority of the community applauded. See if you agree and join the discussion in the comment section to Evolving Distributed Systems.
As a speaker at QCon New York, Michael Uzquiano gave a speech about how to scale API to accept many items. Watch No REST - Architecting Real-time Bulk Async APIs for details about evolving the Evolution of REST over HTTP to transactional, asynchronous bulk operations, and polling methods for job completion including HTTP long polling and WebSockets.
See you in a fortnight! In the meanwhile, send us article suggestions or friendly hellos. Either way, we are happy to hear from you. :)
P.S. In case you’d be interested in trying API2Cart, you can create an account and see how the API works on live stores.