Crafting an Excellent Developer Experience for API Versioning | Nordic APIs |
Versioning doesn't have to mean broken clients and unhappy users. Here are ways to build a great developer experience around API versioning.| Nordic APIs
Versioning doesn't have to mean broken clients and unhappy users. Here are ways to build a great developer experience around API versioning.| Nordic APIs
Today, we'll describe the intricacies of GDPR, then dive into **5 steps to GDPR compliance** that any organization – regardless of size, purpose, or history – can incorporate into their data protection scheme.| 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
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
Here we take an in-depth look at OpenAPI — a good introduction for newcomers and a review for seasoned API developers alike.| 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
With the proper mindset, development approach, and internal API-first considerations, an internal API can be made highly effective and secure.| Nordic APIs
