Using Kubernetes to Build Versatile Microservices

Kubernetes is often talked about, but seldom fully understood system in the API industry. This is largely because containerization, the principle approach that Kubernetes is built upon, is still not nearly as ubiquitous as the classical approach to API design and resource management. 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

Act Now Before The GDPR Deadline

Any data provider worth their salt must be aware of the legal considerations and regulations for their zone of operations. How user data is stored and processed is controlled by a wide range of regulations, and understanding these regulations is key to running a compliant operation. Read more

API Change Strategy

Some people, when confronted with a problem, think “I know, I’ll use versioning.” Now they have 2.1.0 problems.

Brandon Byers

Software Versioning

If your software has a fuzzy or seemingly random versioning scheme — or no apparent version number at all — you’ll likely agree it can be a nightmare to work with. Read more

Is GraphQL Moving Toward Ubiquity?

In a speech at the 2016 GraphQL Summit, Lee Byron of GraphQL/Facebook put forward a “Secret Master Plan” outlining his hopes for GraphQL, the growing API standard.

In an ideal world, he said, he hoped that GraphQL adoption would look something like this:

  • 1–3 months – Hobbyists and personal projects
  • 6 months – Implemented in 3+ languages
  • 9–12 months – New startups and small companies
  • 1.5–2 years – Medium sized companies and products
  • 2 years – Implemented in 10+ languages (actually took ~3 months)
  • 2–4 years – Large companies and tech giants
  • 4–5 years – Ubiquity!
Read more