Incidents During Microservice Decomposition: A Case Study
Fuente:
arXiv
Saved in:
| Main Authors: | , |
|---|---|
| Format: | Preprint |
| Published: |
2025
|
| Subjects: | |
| Online Access: | |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| _version_ | 1866908364300091392 |
|---|---|
| author | Eldenk, Doğaç Çetin, H. Alperen |
| author_facet | Eldenk, Doğaç Çetin, H. Alperen |
| contents | 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. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2505_09813 |
| institution | arXiv |
| publishDate | 2025 |
| record_format | arxiv |
| spellingShingle | Incidents During Microservice Decomposition: A Case Study Eldenk, Doğaç Çetin, H. Alperen Software Engineering K.6.3 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. |
| title | Incidents During Microservice Decomposition: A Case Study |
| topic | Software Engineering K.6.3 |
| url | https://arxiv.org/abs/2505.09813 |