Some people, when confronted with a problem, think “I know, I’ll use versioning.” Now they have 2.1.0 problems.
— Brandon Byers
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
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!
Web APIs are highly variable things – they can be custom-built, designed around a single purpose, all-encompassing, and almost everything in between. Shifting requirements dictate what the interface is comprised of. Due to this, it’s hard to find commonalities between APIs and their user-facing portals. Read more
An Introduction to System for Cross-domain Identity Management (SCIM)
What is SCIM?
SCIM stands for “System for Cross-domain Identity Management” and is firstly a standardized way of representing users, groups, and anything related. Secondly, SCIM helps to standardize methods for acting on this data, such as creating, querying, searching, updating, and deleting. Read more
The OpenAPI Specification is adored, and its usefulness has seen it be subject to sweeping adoption in recent years. It’s clear that many see the value of the OpenAPI Specification, and see value in its adoption.
As with any trend, there’s a certain amount of consideration that should be paid before adopting the solution carte blanche. Read more