Improving Business deliveries using Continuous Integration and Continuous Delivery using Jenkins and an Advanced Version control system for Microservices-based system

For enterprise application various software development models are available. Out of these available software development models, micro-services architecture has gained a lot of popularity. The micro-service architecture fits well to an enterprise applications which are usually complex in nature and requires out of box scalability along with low latency. Micro-services in containerized cloud environment are very useful for enterprise applications. From the software development perspective in a software industry it is also very crucial to identify and rectify the defects at an early development phase rather than at production environment level. Few earlier published works had a focus on micro-services while few others on the issues and challenges of Kubernetes. However, to the best of our knowledge, the relationship between these two has not been worked out earlier. This is the key focus area of this work. This work focuses on identifying the defects at an early stage for micro-services that are deployed on Kubernetes. Few basic guidelines are proposed for a micro-service architecture based on automation, fault design, design philosophy, naming convention, monitoring and warning.