Normally, we find valuable data our clients need, and create APIs. We rationalize our domains into understandable resources, with clear boundaries of ownership (especially in microservice environments). However, if our design doesn’t include considerations for how clients will use the APIs, we can get into a lot of trouble when it goes live. We’ll look at some API design patterns that can cause operational headaches, and how to watch out for them. Furthermore, we’ll cover some tricks to get out of trouble if we already have it implemented.
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High impact blog posts on API business models and tech advice.
Nordic APIs will use the information you provide on this form to provide updates and news.
You can change your mind at any time by unsubscribing from any email you receive from us or by contacting us at info@nordicapis.com. We will treat your information with respect. By clicking below, you agree that we process your information per the terms in our Privacy Policy.
We use Mailchimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices.
Become a part of our global community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.
