Traditional enterprise infrastructure included one or more central servers that were accessed by all client apps. Enterprise server ecosystem used overloaded, complicated in its structure, and difficult to update mechanisms that often duplicated each other’s behavior and functionality.
In the past decades (and even in the last couple of years), we encountered a drastic shift to decentralization, meaning that one service could perform only specific functions (and can be easily replaced without causing serious system failures).
A modern way of building an enterprise infrastructure is based on utilizing dozens of sub-systems that exchange data with each other. But the question here is, how can the data exchange happen if systems use different requests/commands? What if, let’s say, one system supports only queries with a digital signature while the other cannot sign messages?
Our integration platform solves these and many similar compatibility and interaction issues.
The platform implements many patterns described by Martin Fowler in his book “Patterns of Enterprise Application Architecture”.
Our product implements modern B2B protocols such as ebMS, AS2 / AS4, WebServices Reliable Messaging (WS-RM), which makes it possible to use the platform for transactions with guaranteed delivery.
Do you have integration issues within your IT infrastructure? Do you need to “translate” the app into another language? Development of your own solution may not be the best choice in terms of initial costs and further maintenance and support.
Feel free to reach out to us and we will find the best solution.
Our platform can be either installed locally within your company, or used on a subscription basis.
The platform is developed for the companies that need to link multiple services together.
The integration platform can also be used to “connect” the old (legacy) system to the Internet to access its data. You can use it to generate PDF documents from XML files and send them to a remote server or upload to an FTP server.
Almost every enterprise IT department is a subject to these and many similar issues.
The development of your own adapters, bridges and connectors is often more expensive in terms of initial investment, further support and maintenance.
A simple example of the problem that can be solved by our integration platform:
The interaction between system A and system B is not always as simple as: send a request – to get an answer. Quite often communication involves additional conditions, verifications, dependencies, etc. To address the issue of complex integration schemes, we have developed a module that provides service orchestration. This module helps you manage inquiries across various systems, depending on whether certain conditions are met or not.
For example, system A needs to get the information about employee’s salary from system B. But let’s imagine that information about employees is spread across separate systems, depending on the department where the they work in. Before any request is sent to the correct address, you need to know which department an employee belongs to. To do this, you should make a preliminary inquiry and get a department number. Depending on the answer it will be sent to URL1 or URL2. Apart from that, you need to find out whether the user has the right to read employee’s salary. Target request will be performed upon successfull completion of preliminary requests.