Microservices are on the cusp of becoming the dominant style of software architecture in the enterprise. The benefits that are realized—increased developer velocity, improved organizational agility, and reduced time-to-market of new services—are a powerful catalyst that is driving this transformation. As practitioners, how do we successfully fit microservices into the models and processes we already have in place? Join Tom Kerkhove, an Azure Architect with many years of experience helping enterprises make this exact transition, for a hands-on experience demonstrating how he helps enterprises make the transition to API-first architectures and microservices in a hybrid, multi-cloud world.

3. @TomKerkhove
tomkerkhove

4. Meet Codito

5. Where is Codito today?
Products
Shipment Updates
App developers
Orders
Shipments
Codito API

6. The early days of Codito

7. Codito decided to use Azure API Management

8. Codito with API Management
Developer portal
Gateway
Codito API
Management
plane
API
App developers
Discover
Learn
Try
Access
Get help
Shipment Updates
Products
Orders
Shipments
Codito API

9. Codito with API Management
Codito
Codito
Products Logical APIs
Codito API
Codit API

10. As Codito grew, so did their traffic

11. “How about using microservices?”
“Micro-what?”

12. What are microservices?

13. Codito decides to migrate to Microservices
but how do they get there?

14. How do we get there?

15. Codito starts with a “logical” separation

16. Codito’s Initial API Management Approach
Codito
Codito
Products Logical APIs
Codito API
Codit API

17. Codito’s New API Management Approach
Codito
Codito
Products Logical APIs
Codito API
Codit API
Products API
Orders API
Shipments API
Codito - Webhooks

18. Why is this a good practice?

19. How do we migrate without customer impact?

20. Codito with API Management
Developer portal
Gateway
Codito API
Management
plane
API
App developers
Discover
Learn
Try
Access
Get help
Shipment Updates
Monolith on Azure Web Apps
Web Apps for
Containers
Shipment Webhooks
Products
Orders
Shipment

21. Demo

22. Codito’s API Management Approach
Codito
Codito
Products Logical APIs
Codito API
Routeto
microservices
Products API
Orders API
Shipments API
Shipments API
Orders API
Products API
Codito - Webhooks

23. “Hey, we’d like to use Codito but we can’t use the cloud”

24. Management
plane
Gateway Dev portal

25. Enter Azure Arc enabled API Management

26. What is Azure Arc enabled API Management?
 Self-Hosted version of Azure API Management, close to their users
 It’s up to you to deploy, secure, scale, operate & manage the host
 Managed from the cloud, deployed where you need it
 Centralized management in cloud and deploy to one or more gateways
 Gateways are federated to the cloud and require internet connection
 Provides a consistent API experience in Azure, hybrid, and multi-cloud
scenarios

27. Management
plane
Gateway Dev portal

28. Demo

29. Run Codito where the customer is with
Azure Arc enabled API Management

30. What did Codito learn?

31. Build a Monolith first

32. https://www.martinfowler.com/bliki/MonolithFirst.html

33. Building a platform is a journey

34. https://itnext.io/microservices-c8b5dbdd58b8
And that’s ok.

35. Start with PaaS and evolve to Kubernetes and beyond
Focus on your app, not infrastructure.

36. Start with PaaS and evolve to Kubernetes and beyond
API Gateway
App

37. Start with PaaS and evolve to Kubernetes and beyond
API Gateway
App AppApp

38. Start with PaaS and evolve to Kubernetes and beyond
App
API Gateway
AppApp
Ingress Ingress Ingress
Service

39. Conclusion

40. Are Microservices Evil?
Are Monoliths Evil?

41. Use the API landscape your platform requires,
but don’t go all the way unless you have a reason

42. API Gateway helps your platform grow

43. Please evaluate this session
Your feedback is important to us!
https://aka.ms/ignite.mobileapp
https://myignite.techcommunity.microsoft.com/evaluations

44. Find this session
in Microsoft Tech
Community