The typical phase in formulating the tech stack for the next project in your agency is to be clear about how to formulate the requirements for the communication channel of this matter.
A superordinate architectural concept in this respect is coined as Representational State Transfer (REST).
REST originated from the PhD dissertation of Roy Fielding1 in the year 2000.
Fielding’s dissertation outlined REST as a set of guiding principles for designing networked applications, where stateless client-server interactions and the concept of resources identified by URIs (Uniform Resource Identifiers) play a central role.
REST has significantly influenced the design of web APIs and quickly became the dominant style due to its simplicity and scalability.
Here’s the thing: When stopping here you’re missing the good stuff.
Read on tomorrow, when we expand on GraphQL.