**Watch the full webinar at Codefresh.io/events! You have finally split your big monolith into microservices. Now what? How do you validate a more complex application? And how do you make it scale? Instead of having one CI/CD pipeline, you have multiple. And as the number of microservices increases so does the number of pipelines. Managing pipelines for microservice applications can quickly get out of hand, especially when you try to reuse common pipeline parts between different applications. In this webinar, we will see how you can create CI/CD pipelines designed specifically for microservices and how you can reuse the same pipeline across different applications.

1. CI/CD Pipelines for Microservices
Best Practices
DAN GARFIELD & VIDYA SUBRAMANIAN

2. Dan
Garfield
Chief Technology Evangelist
@todaywasawesome

3. Vidya
Subramanian
Principal DevOps Evangelist
@vdevops

4. Agenda
1. Why microservices
2. How Expedia approached
microservice CI/CD
3. How we do it at Codefresh

5. Why Microservices?

7. Monolith 1 Monolith 2

8. Why Microservices?

9. Multiple services with single UI&UXMultiple monoliths with diff. UI&UX
Expedia corporate travel re-architecture
Unified cars UI
Car sortCar search
Cars
(Egencia)
Cars (ECT)
Cars
(Travelforce)
Booking service
Phone apps.

10. Moving to Microservices at Expedia
Approach
● Consolidate code bases and
● Build shared libraries for global platform. Ex:
○ Logging service, monitoring service
● Rely on manual integration testing
● Standardize CI/CD pipelines
● Use Maven for modularity
● Migrate to cloud from on-prem
Issues faced
● Geographically distributed
● Tools consolidation was hard
● Too many pipelines as
microservices grew.
( 100 pipelines → 1000+ )
● Pipelines not modular or
re-usable
● Jenkins master-slave issues
● Copypasta causing bad patterns
● Central team could not keep up
● Plugin upgrade was a nightmare

11. Moving to Microservices at Expedia
Lessons learned and Recommendations
● CI/CD templates should have been prioritized higher than “business needs”
● Bootstrapping new projects should have been externalized from the microservice and
adding a new microservice should have full pipeline setup once a repo is created
● A modular pipeline approach would ease the pain caused by different versions
● Reusability in CI/CD platform is critical

12. Single pipeline per
project
Can be
complex/difficult to
be maintain
Usually led by a single
team (anti-devops)
Organizing pipelines for monolithic applications

13. Scalability issues with microservice pipelines
Does this look
like a plan??

14. Shared pipeline segments are not the solution.

15. Requires everyone to use
same version of library
Libraries often rely on each
other in complex ways
Changes have to go to
admins
Leads to big stability
problems
Organizing pipelines for monolithic applications

16. How Codefresh does
CI/CD for Microservices
1. Container-based pipelines
2. Shared pipelines
3. Deployment testing

17. CODEFRESH ARCHITECTURE DIAGRAM
MULTI CLOUD

18. Each task is built into
a Docker image.
Users can self-serve
these images.
Images DO NOT rely
on each other.
Container-based pipelines

19. Huge open source library at steps.codefresh.io

20. Maintain a single
pipeline
Make microservices
uniform
Change behavior
based on context
Use a single pipeline that operates with context

21. Triggers carry their context
Codebase
Tests
Docker-compose
Helm chart
...
Dependencies
...
Git checkout

22. Demo time!

23. Why Canary?
Usefulness of early testing
Complexity of
Infrastructure
Testing early
becomes less useful
as infrastructure
complexity rises
https://codefresh.io/events/canary-deployment-helm-istio-codefresh/

24. Summary
Shared pipelines > libraries
Reusable Docker images > Copypasta
Deployment validation with canary
Read the blog post at
https://codefresh.io/continuous-deployment/
ci-cd-pipelines-microservices/

25. Questions?
Dan Garfield
@todaywasawsome
Want to try it yourself?
Open a FREE account
today at
Codefresh.io
Vidya Subramanian
@vdevops