Nathaniel Schutta, Software Architect, Jay Lyman, Principal Analyst, 451 Research, Joe Nedumgottil , Principal at Solstice
The agility of microservices appeals to many, but where to start can be a journey in itself. Meanwhile, microservices are often conflated with Kubernetes, the container orchestration platform. This can lead folks down the wrong path by putting the proverbial technology cart before the architectural horse.
When it comes down to it, not everything should be a microservice and not everything should run in Kubernetes. How do you decide when, where, and how to take advantage of this powerful application pattern and technology paradigm combination? Join Joe Nedumgottil, Principal at Solstice, Jay Lyman, Principal Analyst at 451 Research, and Nathaniel Schutta, Developer Advocate at VMware to learn:
- How to determine if an application should be a microservice
- What challenges can you expect with adopting microservices
- What are the advantages of microservices
- From monitoring to logging to service meshes, what do you need to consider for Day Two operations when adopting Kubernetes for microservices
- Why you should look beyond code quality to measure success, including business metrics, with microservices on Kubernetes