IS integration and Connecting Software Connect Bridge
I discovered interesting software a few weeks ago. I was at one meeting with some IT guys and we were talking about possibilities of software integration. If I should say some quick basics, you are able to integrate software between each other in a few different ways/levels/areas. The first one is related to basic / almost prehistoric area. In this scenario, you have to connect everything with everything. So the amount of connection is huge and strictly depend on the amount of source and destination systems.
The second way, how to made integration is to use some middleware, most common workflow manager. In this scenario, we are able to put all the Nintex, K2, SharePoint Designer and other scenarios of developing a workflow in one central place. This workflow uses data connection and it doesn’t matter if these are direct connections to databases, warehouses, to analysis services, to information systems using SOAP or REST. There is the process of getting data through these data connections and after getting there is some business logic on behind – after getting the data. The main problem with these scenarios is that separate information systems have a different nature language for communication. So every connection means the transformation of data, different communication. This is good when you have one solution or basic integration between a small amount of information system, but a little problematic in case that you need some continuous improvements and have a really huge amount of information systems. And this is the reason why big companies thinking about some complex solution for integration. These companies have a huge amount of systems – sometimes tens or hundreds. The important fact is also that in this scenario Business Logic is a part of middleware, so every improvement into this logic means modification of developed workflows/integration.
The third scenario is as it was mentioned some complex solution. This solution is named ESB – enterprise service bus. What does it mean? That company builds something similar to the pipe and connects all the systems to this pipe through data connector which handles the translation of all the communication to universal language – this communication names message orientated communication. But there is another problem. Software for this scenario mostly covers only the pipe creation and environment/framework for development and deployment of such a connector / translator for communication. One of the software for this purpose is, for example, Microsoft BizTalk. But this isn’t a cheap software at all. And after all, you still need a couple of developers to build the connectors. If developers will develop a solution for communication without documentation or will leave the company, the process of development will be really a non-cost saving one. If some smaller company wants to build a nice concept of integration it is almost impossible because of costs as well. And you are able to see in most SMBs that developers just build some simple integration between systems, or some partner/vendor will create a workflow in combination with pre-developed integration with developers.
I am not telling, that there is only this product on the market, I didn’t make any market analysis or research. On the other side, I didn’t find any similar product before, this was the first one, which I heard about and it is really simple in idea – I understand, that there is a lot of development in the background. For me, it was really helpful and this is the reason, why I would like to tell that if you are fans of integration, you should try it.
New product video: https://www.youtube.com/watch?v=bOKTRtHUuKA