How is your stack wired

Deciding on the communication layer for your API driven projects (1/5)

Michael Gerzabek Michael Gerzabek on Sep 3, 2024

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.

  1. Fielding, who was one of the principal authors of the HTTP/1.1 specification, introduced REST as a software architectural style for distributed hypermedia systems, including the World Wide Web. You can read his dissertation online ↩

Michael Gerzabek

About the author

Michael Gerzabek works with engineering teams on system architecture and developer experience in complex SaaS environments.

He writes about the architectural decisions that keep systems understandable long after the first release.

→ Connect on LinkedIn

Stay Close to How We Think About Systems

I write occasionally about system architecture, developer experience, and how complex products stay coherent as they grow.

This is not a marketing newsletter.

It’s a continuation of the thinking behind articles like this one.

If that resonates, you’ll probably want to stay.

    We respect your privacy: read our privacy policy.