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!
How does Conway’s Law impact the way we build effective internal communication within API-first companies?
When we write about web APIs, we inevitably focus on one of two things: The technicalities of building the application itself, or the target market and user base that consumes the API. Read more
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
People develop APIs for all sorts of reasons. They might be trying to create a tool to facilitate internal processes where they work, they could be building an external product for customers, or they might be building a third party tool designed to mash-up other services. Read more
For the longest time, if you wanted to make or receive payments on the web, PayPal was the only option you had. Back then, the process wasn’t necessarily as user-friendly as it is today – but they did simplify how users could transfer money. Read more