Forum

Search
Close
AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

AI Assistant
CI/CD for microserv...
 
Notifications
Clear all

CI/CD for microservices - our multi-repo vs mono-repo strategy

20 Posts
19 Users
0 Reactions
69 Views
(@michelle.gutierrez269)
Posts: 0
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Our experience from start to finish with this. We started about 7 months ago with a small pilot. Initial challenges included legacy compatibility. The breakthrough came when we automated the testing. Key metrics improved: 50% reduction in deployment time. The team's feedback has been overwhelmingly positive, though we still have room for improvement in testing coverage. Lessons learned: automate everything. Next steps for us: optimize costs.

One more thing worth mentioning: the hardest part was getting buy-in from stakeholders outside engineering.


 
Posted : 13/10/2025 5:59 pm
(@maria.carter392)
Posts: 0
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I'd like to share our complete experience with this. We started about 18 months ago with a small pilot. Initial challenges included team training. The breakthrough came when we improved observability. Key metrics improved: 3x increase in deployment frequency. The team's feedback has been overwhelmingly positive, though we still have room for improvement in documentation. Lessons learned: communicate often. Next steps for us: optimize costs.

Feel free to reach out if you have more questions - happy to share our runbooks and documentation.


 
Posted : 15/10/2025 12:00 am
(@rachel.morales858)
Posts: 0
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

This is exactly our story too. We learned: Phase 1 (1 month) involved assessment and planning. Phase 2 (2 months) focused on pilot implementation. Phase 3 (ongoing) was all about full rollout. Total investment was $200K but the payback period was only 9 months. Key success factors: executive support, dedicated team, clear metrics. If I could do it again, I would involve operations earlier.

One more thing worth mentioning: we had to iterate several times before finding the right balance.


 
Posted : 15/10/2025 5:15 am
(@donna.jimenez105)
Posts: 0
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Our solution was somewhat different using Kubernetes, Helm, ArgoCD, and Prometheus. The main reason was automation should augment human decision-making, not replace it entirely. However, I can see how your method would be better for larger teams. Have you considered feature flags for gradual rollouts?

Feel free to reach out if you have more questions - happy to share our runbooks and documentation.

Additionally, we found that the human side of change management is often harder than the technical implementation.


 
Posted : 20/10/2025 9:03 pm
(@benjamin.taylor696)
Posts: 0
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Parallel experiences here. We learned: Phase 1 (6 weeks) involved stakeholder alignment. Phase 2 (3 months) focused on pilot implementation. Phase 3 (1 month) was all about knowledge sharing. Total investment was $50K but the payback period was only 3 months. Key success factors: good tooling, training, patience. If I could do it again, I would start with better documentation.

I'd recommend checking out relevant blog posts for more details.

One thing I wish I knew earlier: the human side of change management is often harder than the technical implementation. Would have saved us a lot of time.


 
Posted : 27/10/2025 5:14 pm
Page 2 / 2
Share:
Scroll to Top