Back in 2006, Google discovered that an extra 500 milliseconds of latency could drop traffic by as much as 20%. That was twelve years ago; now web users expect faster responses than ever before, and as an API practitioner, it’s your duty to make that happen! Read more
Serverless, GraphQL, Go, microservices… disruptive tech offers great benefits, but is “boring” tech better from a pragmatic viewpoint?
If it ain’t broke, don’t fix it. No need to reinvent the wheel. The KISS (Keep It Simple, Stupid!) principle. There are plenty of expressions and the like out there that advocate embracing the tried and tested over the complex and newfangled, but sometimes the siren song of cutting-edge technology is just too much to resist. Read more
Last week Nordic APIs hosted the 2018 Platform Summit, our biggest event to date with about 480 total attendees! Our international assortment of speakers covered a wide spectrum of industries involved in APIs, making it an ideal space to discuss the best practices that will propel the global API industry into the future. Read more
We recently sat down with GraphQL co-creator Lee Byron to learn about the history and future of GraphQL. Hope you enjoy!
The Origins and Future of GraphQLTen years ago Lee Byron was a graphics engineer designing interactive news graphics at the New York Times when a friend approached him to join a small social media startup based in San Francisco, California. Read more
What does it mean in programming to be idempotent? Today, we’re going to look at the concepts of idempotence and safety, and identify what makes them so very important in the context of web API design.
We’ll compare idempotence and safety to see how they’re different, and discover why this division is important. Read more
