Posts Tagged: GraphQL

Is REST Still a Relevant API Style?

What kind of API style should you be using? From SOAP, to REST, GraphQL, and new styles like gRPC, there are many competing standards for designing APIs and the way consumers interact with them. We’ve written about each before, but as the industry changes rapidly, there are always new concerns and opportunities for comparison. Read more

Federated Data With HyperGraphQL

Is HyperGraphQL the linked data extension for GraphQL we’ve been waiting for?

Data, in many ways, is the driving force behind much of what the information technology industry does to innovate. Each choice is informed largely by one’s ability to find data, secure that data, and then form relationships within a web of unconnected points. Read more

Making Fast APIs: Lessons Learned From 40 Years of SQL

SQL is old — about 40 years old, in fact. In the tech world, where a new framework or language pops up seemingly every day, 40 years feels downright archaic. Why is such an old language relevant to building APIs in 2018? 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