An API First Approach to Designing Software
At Anomaly, we pride ourselves on building things with the future in mind. A portion of this is achieved by our approach towards software development—something which I have been meaning to write about for a little while now. The transformation of how we write software stems back to our realisation that Application Programming Interfaces (APIs) have become the centre of software platforms; it's the new business logic layer of Internet-based software. End user interfaces are one of many facets of this central source of truth. The embodiment of our belief in APIs is Prestans, a single purpose framework helping developers build robust APIs.
Prestans 3, a ground-up reboot of our WSGI-compliant REST framework, is underway and we anticipate shipping a release before the year folds. This is part of our commitment towards building software with great habits and pushing the envelope towards Python 3. I will discuss Prestans 3 at a later date, when we have more to share.
There has been a lot of talk about mobile first, putting the desktop in the back seat and heading for the mobile, neglecting to highlight that they're all powered by backends accessible via an API.
Five years ago we realised that for applications of the future, the Web was going to be one of many interfaces. We turned our focus towards what we call API first, building applications that, on day one, ship with an API—ours, of course, built using Prestans. We've moved from building applications to building platforms, each one of them featuring an API.
A new and detailed part of our website on our unique approach to building software is under development, and I will continue to reflect on the building blocks that make our approach stand apart.