Basically, microservices serve the purpose of software modularization. This possibility becomes more relevant the more heterogeneous the IT constellations are. By using microservices, you can separate big projects into smaller units or services so as to maintain them individually and independently from one another.
Through a clever division of the overall architecture into sub-sectors, microservices deal with individual process steps separately. This approach modularizes the software and significantly simplifies the scaling of individual sub-sectors.
The process (BPMN) and the function (UML) of the application are defined in a process model. On this basis, Scheer PAS generates a functionally equivalent xUML state machine with persistent states – a very efficient function, since the generated service can be immediately packetized and used. In the basic version, this service writes log messages for each status transition, but you can add your action implementation models consecutively, so as to start with a fully functional process from the outset.
For simple, synchronous integration services you can skip this step and directly implement your synchronous retrieval logic.
The magic part comes last: running the model without the intermediate generation of codes.
Furthermore, individual microservices are not implemented under some monolithic dome but are handled and executed as independent processes during runtime and even on the operating system level – centrally managed in the Scheer PAS integration layer.
Minimum resource requirements: Our solution scales almost linearly. Small processes or sub-sections in particular require little attention, so there's no significant overhead.
Problems in one place don't affect other services: Scheer PAS solutions are very stable. Services can, independently of one another, be put into operation or replaced by new versions. Similarly, at peak times or in case of resource bottlenecks, other microservices can be implemented quickly and flexibly in Scheer PAS.
No downtime: provision of a service takes 2-3 seconds. Each integration path can therefore be implemented as a separate service and exist independently – ideal for an iterative procedure for complex solutions.
Why should you rely on microservices in IT integration?
Looking for a flexible and stable solution with minimum hardware requirements, without having to enter cloud contracts? Talk to us!
Your contact person
Fabian JansenExpert Sales Management
© 2022 Scheer GmbH
Necessary cookies enable basic functions and are required for the proper functioning of the website.
Statistics Cookies collect information anonymously. This information helps us understand how our visitors use our website.
Marketing cookies come from third party providers, these collect information to play out targeted content.
In order to display content from video platforms and social media platforms, cookies are set by these external media.