Monolith might be better than micro services

English System design

Draft Disclaimer: Please note that this article is currently in draft form and may undergo revisions before final publication. The content, including information, opinions, and recommendations, is subject to change and may not represent the final version. We appreciate your understanding and patience as we work to refine and improve the quality of this article. Your feedback is valuable in shaping the final release.

Language Mismatch Disclaimer: Please be aware that the language of this article may not match the language settings of your browser or device.
Do you want to read articles in English instead ?

  • micro services might not be for you
  • small problem small solution
  • use the right tool
  • no hammer to kill a fly
  • you can still use domain driven to split code into own section
    • this encourage code reuse
    • allows any part that grows too big to be its own microservice
  • facilitate removal following single responsability principle
  • strategy around data removal
    • migration from old to new servers
    • removal of the old data
      • soft delete rename to tmp name appending suffix
      • real deletion next release if nothing broke
Babacar Cissé DIA
By on

A Solutions Architect and Developer who thrives on crafting digital solutions. Passionate about learning and innovation, he sees challenges as opportunities to build secure, responsive, high-quality applications that drive business growth through cutting-edge technology. His blog serves as a tech memoir, documenting his coding journey and sharing insights into software architecture. It’s a blend of lessons, musings, and tech expertise, providing a glimpse into the art of crafting solutions in an ever-evolving digital landscape.