Migration aspects from monolith to distributed systems using software code build and deployment time and latency perspective

The transition from an error-prone, slower, and extremely high-volume legacy system like monolithic system to a faster, lighter, and error-freemicroservices based system is not always so simple. Microservices areindependently deployable and allow for a better team autonomy. In this work,several migration efforts to migrate from a legacy based monolithic system toa pure distributed microservicesbased system has been tested and deployed in keeping two DevOps principles, the software code build and deployment time and latency in monolithic and microservices. Some real-time projects are considered to measure the performance and the time taken to execute the experiments. To measure the total build and deployment time and latency, Jenkins, Prometheus, and JMeter are installed which are industryrecommended softwares. It is observed that there is a total of 7 seconds taken to build and deploy at containers for 10 microservices whereas 10 monolith applications took almost 260 seconds to be built and deployed to the application server. While increasing more requests per second it is observed that upto 3000 requests per second, it impacted the response time of monolith applications but microservices stays the same. The main conclusion is that microservices are rarely impacted in response time with respect to requests per second.