What are REST APIs? How do they work, and what differentiates them from SOAP? All the basics of what an API looks like, what are requests and responses, HTTP methods. The next one coming up in the same series briefs REST APIs with respect to their architectural constraints. That’s where we find the real potential of using REST for building APIs for any application. And the next few that I’m writing on this series are developing APIs based on REST.
How does Computers communicate?
Recently, during a job interview, I was asked questions about what REST APIs are. How do they work, and what differentiates them from SOAP? And, as easy as it might be for many, for me it’s something I’ve never spent much time on studying or understanding to their depth. It’s one of those topics I have never got a chance to explore. Never was required for any of my previous projects. And I feel it’s a very relatable topic if someone is in Software Development. Almost all of my friends and colleagues have good knowledge on them or have worked on them as part of their previous projects. That’s why I feel it’s high time for me to take a leap towards understanding REST APIs.
So, this article is about exploring REST APIs, how they work and why do we need them. I have a few more articles to come up in the same topic, or rather I can say a series of articles.
This article covers all the basics of what an API looks like, what are requests and responses, HTTP methods, and some more terminologies which might be required further. The next one coming up in the same series briefs REST APIs with respect to their architectural constraints. That’s where we find the real potential of using REST for building APIs for any application. And the next few that I’m writing on this series are developing APIs based on REST.
What is REST? The REST acronym is defined as a “REpresentational State Transfer” and is designed to take advantage of existing HTTP protocols when used
I’ve been working with Restful APIs for some time now and one thing that I love to do is to talk about APIs.
APIs can be as simple as 1 endpoint for use by 100s of users or as complex as the AWS APIs with 1000s of endpoints and 100s of thousands of users. Building them can mean spending a couple of hours using a low-code platform or months of work using a multitude of tools. Hosting them can be as simple as using one platform that does everything we need or as complex as setting up and managing ingress control, security, caching, failover, metrics, scaling.
Representational state transfer (REST) is a style of software architecture. As described in a dissertation by Roy Fielding, REST is an "architectural style" that basically exploits the existing technology and protocols of the Web. RESTful is typically used to refer to web services implementing such an architecture.
APIs - the current “big thing” - offer the opportunity for modern organizations to unlock new and lucrative business models. The article below covers some tips on how to spin the API flywheel and leverage its possibilities.