Giving thoughts

Although the new approaches originate from different disciplines, they share the same two old and well known concepts: Divide & conquer and Inspect & adapt . Why these approaches? – Because we naturally fail. Today’s digital globalization requires highly integrated IT systems with rich functionality. In order to develop and operate such large and complex IT, we cannot simply scale the projects. Instead, we come up with new approaches such as MVPs in product management, Microservices in IT architecture and agile methods in project management. Why these aspects? – Because they are crucial for successful IT products. Product management focusses on the outcome - the IT product – from an external perspective. Whereas IT architecture defines the internal structure of the IT product. And project management considers the people and processes in order to manage limited time, resources and features respectively quality, since products are usually developed as project. Agile

Today, we have a lot of monolithic system running. The future system landscape, however, will be micro services – a flexible and scalable architecture. Why we move towards micro services is clear: First, because micro services are more flexible and scalable than old approaches such as monoliths. Second, due to the diversification on operational level, we get a robust system as a bunch of resilient services. The overall system does not stop, if only one services stops working, and it might heal itself. And last but not least, because we can! Can we? How do we actually transform a monolith towards a micro service architecture? Since monolithic are usually build out of modules, my answer is: We transform a monolithic into a micro service architecture based on its modules, which support the users business cases. Background In general, IT facilitates the principle of divide and conquer in order to handle complexity. A large problem is cut into smaller, manageable pieces. Monolit