Using Canary Release To Ease API Versioning | Nordic APIs |
How does a canary release strategy stack up to traditional REST API versioning? Understand how API providers can benefit from a canary release plan.| Nordic APIs
How does a canary release strategy stack up to traditional REST API versioning? Understand how API providers can benefit from a canary release plan.| Nordic APIs
Once an API is updated, versioned, or otherwise changed, what is the best way to communicate that to a developer user base? We discuss 6 strong ways to communicate API change.| Nordic APIs
Continuous versioning replaces typical URI versioning (v1, v2, etc) to withhold the server to client bond, equating to consistency and better API agility.| Nordic APIs
What are breaking changes? And how can we avoid them? Here are best practices to avoid and mitigate breaking changes for your API designs.| Nordic APIs
Breaking API changes don't have to break your client integrations. Learn the best practices for effectively managing breaking changes.| Nordic APIs
Far different than traditional software versioning, API versioning can have complex implications for the products using it downstream. In this article we cover the most widely used approaches in the API space, including traditional URI versioning, using the Accept Header, continuous versioning, and more.| Nordic APIs
We compare two ways to update a web API – revisions are incremental, non-breaking changes to an API, whereas versions are often-breaking, major changes.| Nordic APIs
Breaking changes are worse if API consumers can't detect them at all. Here are five ways to spot breaking changes in your API integrations.| Nordic APIs
