Modern API design isn’t just about choosing what technology to use. It’s about building systems that must satisfy regulatory compliance AND high performance, international scaling AND appropriate security, legacy integration AND modern architecture, all simultaneously. Drawing from experience building APIs at Goldman Sachs (financial regulations) and Personio (international HR), I’ll share practical patterns for API architecture when you can’t just optimize for one dimension.
You’ll learn: – How to identify and prioritise conflicting requirements – Data modelling approaches when privacy laws conflict with other requirements – Real examples from Payroll APIs serving multiple jurisdictions, and combining lots of input data
Key takeaway: A framework for constraint-driven API design that turns requirements headaches into architectural advantages.
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.
By clicking below, you agree that we process your information per the terms in our Privacy Policy.
Ranked #1 API blog on the web
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.
