Posts Tagged: versioning

An Introduction To API Economy Boosting Principles

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

Don’t Let API Changes Hit You Like A Freight Train!

Most web applications, and many mobile applications, rely on 3rd party APIs like social login, cloud storage, email, messaging, CRM etc. The benefits are obvious, and for some applications the API integration is a core element. However, the API dependency does make applications more vulnerable to change — one small change to an API can break an entire app. Read more

Best Practices for A Healthy GraphQL Implementation

We’ve discussed GraphQL at length previously – and while the discussions on how GraphQL works are obviously very powerful, we’ve yet to dive into some of the best practices that should be adopted when developing a GraphQL-centric API.

Today, we’re going to do exactly that. Read more

Security Points to Consider Before Implementing GraphQL

GraphQL is a very powerful query language that does a great many things right. When implemented properly, GraphQL offers an extremely elegant methodology for data retrieval, more backend stability, and increased query efficiency.

The key here though is that simple phrase — when implemented properly. Read more

Continuous Versioning Strategy for Internal APIs

Recently, there has been debate over what the best practices are for versioning an API. Many public web APIs are retired as new versions replace them, but if you were to ask Roy Fielding, creator of REST, he may tell you not to version your API at all. Read more