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!
Node.js is one of the most commonly used technologies in the web space. According to the StackOverflow 2017 survey, 47.1% of respondents who utilized frameworks and libraries utilized Node.js as a primary technology.
This love is really no surprise – efficient, lightweight, and powerful, Node.js includes npm, the world’s largest open source library ecosystem, providing extensibility that has to be seen to be believed. Read more
We’ve previously talked about Go – it’s a very powerful, efficient, and lean language that powers both enterprise and small group applications. While Go itself is very powerful, as with any language, additional functionality is often desired, or outright required.
When those situations arise, having a solid framework with which to depend on is very important. Read more
PHP is a powerful language, with a wide range of offerings that make utilizing it for anything from basic websites to complex APIs a very strong proposition. It’s got a wonderful low barrier of entry, a gigantic ecosystem of solutions, and a variety of framework implementations that can make it do almost whatever you dream. Read more
The API lifecycle is a topic of much discussion — and rightfully so. The API space is agile, ever changing, and its participants must continually meet the shifting kaleidoscope of user needs and demands.
Speeding up and securing this lifecycle is seen by many, then, to be the Holy Grail. Read more