Posts Tagged: Design

REST State Machine Revisited

In the months after the publication of Designing a True REST State Machine and the talk it was based on, there has been quite a bit of discussion and the questions posed should be addressed. While each could be responded to individually, perhaps they might be better served by writing everything up in a blog post. Read more

Why You Should Be Designing APIs to Spec

There’s a good reason why building APIs can be extremely tough and time-consuming: they have to cater to both human and machine needs.

Inherently, this is pretty difficult. Machines are picky and rely on pure logic; they crave rigid, hierarchical structures and definite instructions. Read more

7 Growing API Design Trends

The API world is one of constant evolution and mutation. The data that we dealt with in the 1990s is not the same as the data we might deal with in 2017, and because of this, our APIs have had to drastically change in their approaches. Read more

Using-A-Schema-First-Design-As-Your-Single-Source-of-Truth

Using A Schema-First Design As Your Single Source of Truth

One of the hardest parts of developing a product is the coordination of so many teams and moving parts. Ensuring that everyone is moving in the same direction, towards the same goal, and in a way that is complimentary is the single most important – but also the single hardest – element of any collaborative project. Read more

What it means to have a full spectrum API

What It Means To Have A Full Spectrum API

Expanding The Scope Of Your API

In development, the term full stack – familiarity with multiple programming languages for both frontend and backend development – is thrown around pretty regularly. Full spectrum is one that’s used from time to time, and may be a better way to describe the techniques required for superior API practice. Read more