Posts Tagged: Representational State Transfer

Is REST Still A Good API Design Style to Use?

We interview three experts on the state of REST API design

Representational State Transfer, or REST, is a dominant architectural pattern. Since Roy Fielding conceived it in 2000, REST has become the predominant method to design robust web APIs. However, with the advent of new application demands, some question whether REST is right for every single use case. Read more

REST vs Streaming APIs: How They Differ

REST vs SOAP. REST vs GraphQL. JSON vs XML. There are many dichotomies in the world of API design. It seems for each architectural choice there exists an opposite solution purpose-built for a specific application. We can see this in issues like statelessness and statefulness, as well as functional choices such as SOAP and REST. Read more

A Pragmatic Take On REST Anti Patterns

Do you ever have those moments when you’re asked to do something that feels technically wrong? Putting milk in the cup before the tea? (a very British problem admittedly). An overflowing trash can YOU must always empty? We all have our pet peeves — it’s what makes us human. Read more

REST State Machine Revisited

In the months after the publication of Designing a True REST State Machine and the talk it was based on, there has been quite a bit of discussion and the questions posed should be addressed. While each could be responded to individually, perhaps they might be better served by writing everything up in a blog post. Read more

An Introduction to APIs For the Uninitiated

If you have arrived at the Nordic APIs blog there is good chance you have some inkling of what an API is and why you might need one. However, for the uninitiated, APIs (Application Programming Interfaces) and especially the API economy can be a confusing and fragmented space with some loose standards, an incredible amount of diversity, and a seemingly impenetrable barrier of technical jargon. Read more