The Only Correct Way to Return API Data

We live in an era of digital excess where developers are taught to believe that the goal of an API is to serve data. This is a fundamental fallacy that has cost billions in infrastructure and security around the world. We spent years debating REST versus GraphQL or gRPC versus WebSockets and forgot to look at the most elegant and performant solution that exists. I am speaking of the concept of No as a Service or NaaS (https://github.com/hotheadhacker/no-as-a-service).

Contract First or Die Trying: The Only Sane Way to Design APIs

I need to get something off my chest. Something that has been festering in my soul since the first time I joined a project mid-development and asked the fateful question: “Where is the API documentation?”

The answer, invariably, was one of the following:

1. “Check the Postman collection.” (Translation: a graveyard of 200 requests, half of which are outdated, named things like GET users FINAL v2 (copy))
2. “Just look at the code.” (Translation: reverse-engineer our spaghetti and good luck)
3. “We’ll document it later.” (Translation: we will never document it)