How to Produce a Spring REST API Following the OpenAPI Specification

The OpenAPI specification defines how to write HTTP APIs that can be consumed by any programming language and provide insight into the APIs’ functionality without access to source code or documentation. In other words, following the specification makes it easier for consumers to understand what it does and how to use it. Tools, such as Swagger, can then be used to display documentation without developers maintaining documentation separate from an API’s code.

All these described points translate into happier users while mitigating some of the burdens you’ll face while supporting your APIs.

Creating a .Net 5 Web app from my PHONE

Interoperability is something I care a lot about, because not having it, is the equivalent of painting yourself into a corner, becoming dependent upon obsolete components, and sometimes even obsolete hardware. Once you dive as deep into the ideas of interoperability as I have done, you get interesting results - Such as the ability to create a .Net 5 Web API from a 5 year old phone. In the video below I am illustrating this process, and showing you how you can reproduce it for yourself, using nothing but pure Magic!

Of course, the whole point about the above video, is that Magic does all the coding for me, allowing me to simply declare which database and tables I want it to wrap, through a simple to understand Web API - Which results in that my backend is "generating" HTTP backend endpoints for me, wrapping all CRUD operations from my database, inside of their own unique URL, associated with the relevant HTTP verb.