When transitioning to microservices, start with the components that offer the most flexibility and immediate business value. I typically focus on the areas that are high-impact but relatively independent. In one project, we began by migrating the authentication and user management services. These were isolated enough to avoid breaking dependencies but critical enough to show tangible benefits early on. It’s about picking the low-hanging fruit that will get buy-in from the team and stakeholders while laying a solid foundation for future migrations. Always remember—don’t boil the ocean, migrate piece by piece.

Quick wins are only possible for loosely coupled components/services. To check the feasibility of the new approach and also the new proposed platform (e.g. a container platform like kubernetes), I recommend starting with a simple microservice that can be easily connected via APIs. To do this, you need to know the dependencies in your existing application and also at database level. Once this is successful, I recommend looking for microservices with a high demand for changes.