Categories: TechnologyWeb

"Web" vs "REST" APIs

If you are a RESTferian or REST-fanatic, please look away now. This is my regular rant about the term “REST” 🙂

<rant>

I am seeing the term “REST” everywhere these days, as an annotation of things that obviously do not follow the architectural principles expressed in Fielding’s thesis. Also, when someone implements all the REST principles with CORBA or even SOAP (remember that WS-Web experiment?), how are we going to call the APIs then?

What’s wrong with “Web APIs”? It’s beautiful, it captures the fact that they are APIs for the Web and by the Web and doesn’t tie anyone to a particular architectural style. You take advantage of the Web Architecture’s features that make sense to your application and everyone’s happy 🙂

</rant>

Will probably have to repeat in few months just so that I can take it off my chest 🙂 I know what Jim will probably say… “just move on” 🙂

Recent Posts

Playing with graphs and neo4j

After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…

2 weeks ago

A Graph Model DSL

Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…

1 month ago

BrainExpanded – Web app and Data Sources

As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…

1 month ago

BrainExpanded – End-to-end working

Imagine a world where your memory is enhanced by a team of intelligent agents, working…

2 months ago

BrainExpanded – Login State Caching Issue in iOS Share Extension

As part of the BrainExpanded project, I’m building an iOS app that lets users easily…

4 months ago

Is AI Good or Bad?

Artificial Intelligence (AI) has rapidly evolved over the past few decades, becoming an integral part…

4 months ago