One for all: This used to be the guideline for software solutions. In the meantime, the paradigm has changed. The all-embracing, maintenance-intensive system has had its day. Instead, software engineers rely on fragmented solutions based on a modular system.
In concrete terms, this looks like this: A company puts together individually combinable modules for a customer portal. It chooses the micro-service of an Australian provider for checking the syntax of mail addresses. A micro-service from a German agency is used for the dispatch. A further module from a third party provider encrypts the data. For the CMS of one of our customers, about 200 micro-services were used.
All these modules work independently of each other. They can be exchanged easily without affecting the functionality of the entire system. A clear advantage compared to the previous, cumbersome systems.
Although this development has been going on for some time, micro-services and service-oriented architecture are only now becoming established on the corporate side.