Incidents During Microservice Decomposition: A Case Study

May 14, 2025 Β· Declared Dead Β· πŸ› International Conference on Evaluation & Assessment in Software Engineering

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors DoğaΓ§ Eldenk, H. Alperen Γ‡etin arXiv ID 2505.09813 Category cs.SE: Software Engineering Citations 0 Venue International Conference on Evaluation & Assessment in Software Engineering Last Checked 5 months ago
Abstract
Software errors and incidents are inevitable in web based applications. Scalability challenges, increasing demand, and ongoing code changes can contribute to such failures. As software architectures evolve rapidly, understanding how and why incidents occur is crucial for enhancing system reliability. In this study, we introduce Carbon Health's software stack, share our microservices journey, and analyze 107 incidents. Based on these incidents, we share insights and lessons learned on microservice decomposition. Finally, we suggest that starting with monolithic modularization as an initial step toward microservice decomposition may help reduce incidents and contribute to building more resilient software.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted