On November 11, 2020, I had the pleasure of speaking with two incredible thought leaders in the DevOps space: Vivek Pandey, VP of Engineering at Shipa (http://www.shipa.io), and Patrick Deuley, Sr Product Manager at GitLab (https://www.gitlab.com). The topic of the discussion was “Monolith to Microservices,” and we covered three key areas: Starting out, Scaling and Developer Experience.
GETTING STARTED WITHOUT A COOKIE CUTTER:
By 2022, IDC predicts that 90% of all new apps will feature a microservices architecture. Some of the drivers behind that are the improved ability to design, debug, update and leverage third-party code, and more. However, transitioning an existing application from a traditional monolith architecture to microservices architecture can be very challenging. How do we get started down the microservices path?
SCALING, AKA “BLOWING THINGS UP”
Often times, teams get really excited once they start to see benefits from a microservices architecture, and they start migrating everything. But scaling brings in an entirely new set of challenges. Gone are the days of simply throwing more load balancers at the problem. What are some additional challenges that teams are going to encounter when they start to scale and what are some strategies that can help them address some of these things?
THE DEVELOPER EXPERIENCE – “IT’S SO COMPLICATED”
What changes for a developer in an object-oriented architecture? Are there additional complexities? And if so, what are some strategies to improve their experience and allow them to focus on writing code, instead of thinking about clusters and YAML files and all the other things that come along with microservices and Kubernetes?
See how Ship and GitLab integrate to provide a powerful combination for tackling many of these challenges HERE