Previous proposalVirtuous Cycles: Enabling SRE via automated feedback loops
Next proposalOLTP or OLAP? Why not both?
Decomposing a Monolith: Engineering and Operational strategies we have gleaned from our experience at Endurance
Submitted by Sudheer Kumar Meesala (@sudheerm) on Monday, 6 May 2019
Section: Full talk Technical level: Intermediate Session type: Lecture Section: Sponsored talk Technical level: Intermediate Status: Confirmed & Scheduled
Microservices are all the rage nowadays. But what are the practical problems of building a large application using such an architecture? Even more important, how do you change a business critical legacy application to microservices while maintaining uptime. At Endurance, we are currently transitioning a large legacy monolithic application to a microservice based architecture. There are several key issues around this transition that we have had to address. This talk examines each of those issues in detail and the solutions that we came up with.
Our APAC story in identifying and addressing the key issues around moving ~$70 million dollar monolithic Domain provisioning & Billing platform to microservices:
Need for micro-services
Managing the transition
Scaling, Redundancy and Deployments
Sudheer Kumar Meesala has spent the last few years designing and building scalable and secure web applications in the Finance and Internet industries. A large part of his job has included decomposing monolithic legacy applications into microservices. This has required a deep understanding of PostgreSQL, Cassandra and other NoSQL databases. Other key areas of interest are container orchestration, DevOps and more. He lives in Bangalore, India and spends far too much time in traffic jams.
He is an accomplished speaker and trainer; Co-author of “PostgreSQL 11 Administration Cookbook”.