Following the old tradition, let’s start your week with a cup of coffee or tea, tasty breakfast and a portion of news. In today’s edition you will find a brief overview of the following articles:
- DZone Research: How APIs Have Changed Application Development
- REST APIs And Business Benefits
- The Power of HTTP for REST APIs — PART 2
- Why I love GraphQL
- Public Awareness for APIs Sucks. Here’s What We Can Do.
- REST was NEVER about CRUD
- API Microgateways
1. DZone Research: How APIs Have Changed Application Development
The new Gartner Critical Capabilities report explains how APIs and microservices enable digital leaders to deliver better B2B, open banking and mobile projects. Tom Smith denotes that according to the research, APIs have made the creation of applications faster, resulting in more flexible applications, while giving developers the opportunity to reuse code.
2. REST APIs And Business Benefits
APIs are so powerful that within Amazon all teams/departments exchange data & functionality only through APIs. But, what REST APIs really are? In this article Sohail Jaffry defines the benefits of REST APIs and the reasons why you should ask your development team to build your application with REST API.
3. The Power of HTTP for REST APIs — PART 2
In part 1 James Higginbotham covered the basics of using HTTP to help us design robust REST APIs. For part 2 he dives into a little more specificity such as hypermedia API, HATEOAS, and Caching. Applying these techniques allows to build robust APIs that drive complex applications that are both resilient and evolvable.
4. Why I love GraphQL
In this article Budac Grigore tells about GraphQL, the reasons why it was developed and why he loves it, as well as defines where GraphQL sucks and predicts its future. Check out the article to get know more about it.
5. Public Awareness for APIs Sucks. Here’s What We Can Do.
Technology competence is on the rise, and APIs are the one big thing that’s shaping how modern gadgets develop — so why has nobody heard of them? Thomas Bush answers this question providing a number of reasons and the ways to increase public awareness around APIs.
6. REST was NEVER about CRUD
A popular myth is that REST-based APIs must be CRUD-based – that couldn’t be further from the truth. It is simply one pattern in our API design toolbox. In the article James Higginbotham outlines a variety of additional patterns available for REST-based APIs. The intent isn’t to be fully exhaustive, but to open the options for API designers uncertain about how to apply designs beyond CRUD to REST-based APIs.
7. API Microgateways
In this article Robert Wallach from Stoplight discusses the kerfuffle around API Microgateways. He explores the history of the API gateway on three phases, explains of what API microgateway is, which functions it performs and what its pros and cons are.
In case you are interested in unified shopping cart API, your best choice is API2Cart. Click the button below and schedule a call with our expert.