{"id":21135,"date":"2019-10-03T11:48:20","date_gmt":"2019-10-03T10:48:20","guid":{"rendered":"https:\/\/www.devopsonline.co.uk\/?p=21135"},"modified":"2019-10-03T11:55:17","modified_gmt":"2019-10-03T10:55:17","slug":"how-to-build-a-continuous-integration-and-continuous-deployment-pipeline-for-your-enterprise-middleware-platform","status":"publish","type":"post","link":"https:\/\/devopsnews.online\/how-to-build-a-continuous-integration-and-continuous-deployment-pipeline-for-your-enterprise-middleware-platform\/","title":{"rendered":"How to build a continuous integration and continuous deployment pipeline for your enterprise middleware platform"},"content":{"rendered":"

With the rise of microservice architecture (MSA), continuous integration (CI) and continuous deployment (CD) has become mainstream processes within enterprises. Those familiar with microservice architecture<\/a> will no doubt have heard about greenfield and brownfield integrations, a route where, around 80% of the time, users start a microservices journey from scratch or from an existing enterprise architecture.<\/p>\n

According to a recent survey<\/a> from Lightstep, \u00a0there are more and more organisations moving ahead with microservices architecture, even though they accept that it is hard to maintain and monitor.<\/p>\n

Moreover, the survey highlights that the advantages of MSA outweigh the disadvantages. This also goes for CI\/CD in that it is a tightly coupled concept along with MSA and adopting a DevOps culture.<\/p>\n

Due to the dominance of MSA within enterprises, CI\/CD has also become an essential part of each and every software development lifecycle within enterprises.\u00a0 With this shift towards MSA, DevOps and CI\/CD, other parts of the brownfield integration cannot stay out of these waves. These include:<\/p>\n