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).