The initial state of a hardware control application was not a simple monolith but a messy mix of C# WinForms and C++ services.
Unplanned monoliths often lead to tangled dependencies, deployment challenges, scaling issues, and code that is difficult to understand or modify.
A modulith combines the deployment simplicity of a monolith with the organizational benefits of modules based on business-bounded contexts.
While microservices offer independent deployment, a modulith optimizes for a single runtime environment, reducing network overhead and improving resource efficiency.
Modules are built around a domain model with public interfaces, allowing internal implementations to be swapped without affecting other parts of the system.
A modular architecture simplifies support for multiple product generations and hardware variations by enabling interchangeable component implementations.
The system is organized into distinct layers for hardware, assets (domain entities), features, and product configuration, all built on a shared foundation platform.
The refactoring process involves wrapping the legacy system as the first module and then systematically extracting new, independent modules based on domain models.
27:19Pratishtha Pandey
25:05Eberhard Wolff
43:13Carola Lilienthal
1:01:30Henning Schwentner
50:06Jens Happe
26:45Babette Wagner
24:38Carola Lilienthal
43:07Adam Mullen & John Collins
.gif?w=240&auto=compress,format)
.gif?w=240&auto=compress,format)
.gif?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
M&M Software GmbH
Sankt Georgen im Schwarzwald, Germany
Wilhelm Ag
Lionstep AG
Berlin, Germany
Vesterling Consulting GmbH