Manish Singh Teksmobile
Designing a whole API program is certainly not a kid’s play. When you design an API program for an enterprise, there are many components involved . On a high level they can be divided into following parts: – Front end or app – API gateway or exposure layer – Microservices or Back end service – Developer Portal or Dashboard
This session deals with which activity or logic should be kept in which of the above components and why so? These best practices would be explained with help of use cases and examples.
This post is older than 4 years. External links has been removed
October 11, 2017 13:20
Stora Stjärnrummet (11th floor)
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.
Become a part of the world’s largest 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.