Skip to main content

Integration support

With you every step of the way...

 

Eonic has a wealth of experience in delivering software into new digital environments. We provide a range of support services to advise and facilitate its integration, ensuring maximum benefit to your business.

 
 
 
Clouds-layer-blue-sm
Clouds-layer-white-sm
 

We integrate to make things great...

 

System integration often involves us taking disparate systems needing to communicate with each other in such a way that focuses on increasing value to you, our customer (eg. improved product quality and performance), but at the same time providing value to your business (eg. reducing costs and improving efficiency). In the digital world, more and more systems are designed to connect, both within the system under construction and to systems that are already deployed.

Okay, this is where logical thinking takes precedent over pretty prose...so, take a deep breath and read on!

Vertical integration is the process we use to integrate subsystems according to their functionality by creating functional entities, also referred to as silos . The benefit of this method is that the integration is performed quickly and involves only the necessary vendors, therefore, this method is cheaper in the short term. On the other hand, cost-of-ownership can be substantially higher than seen in other methods, since in the case of new or enhanced functionality, the only possible way to scale the system would be by implementing another silo. Reusing subsystems to create other functionality is not possible.

All clear? Great...then on to the next methodology...

Star integration , also known as spaghetti integration , is where our engineers integrate each system that's interconnected to each of the remaining subsystems. When observed from the perspective of the subsystem which is being integrated, the connections are reminiscent of a star, but when the overall diagram of the system is presented the connections look like spaghetti. The costs are more variable like this because of the interfaces that subsystems are exporting. In a case where the subsystems are exporting heterogeneous or proprietary interfaces, the integration cost can rise substantially. Time and costs needed to integrate the systems increase exponentially when adding additional subsystems. From the feature perspective, this method often seems preferable, due to the extreme flexibility of the reuse of functionality.

Are you still with us? Okay, on to the next method...

Horizontal integration or Enterprise Service Bus (ESB) is an integration method in which a specialised subsystem is dedicated to communication between other subsystems. This allows cutting the number of connections (interfaces) to only one per subsystem which will connect directly to the ESB. The ESB is capable of translating the interface into another interface. This allows cutting the costs of integration and provides extreme flexibility. With systems integrated using this method, it is possible to completely replace one subsystem with another subsystem which provides similar functionality but exports different interfaces. All this is completely transparent to the rest of the subsystems. The only action required is to implement the new interface between the ESB and the new subsystem.

The horizontal scheme can be misleading , however, if it is thought that the cost of intermediate data transformation or the cost of shifting responsibility over business logic can be avoided.

Common data format is an integration method to avoid every adapter having to convert data to/from every other applications' formats, Enterprise application integration (EAI) systems usually stipulate an application-independent data format. The EAI system invariably provides a data transformation service as well to help convert between application-specific and common formats. We do this in two steps:

  • The adapter converts information from the application's format to the bus's common format, then...
  • Semantic transformations are applied on this (eg. converting post codes to city names, splitting/merging objects from one application into objects in the other applications, and so on).

And there you have it...system integration support in a nutshell. The great news for you is Eonic shoulder all the strain and pain: Amongst other things, we:

  • Work with you to analyse your business requirements
  • Understand the drivers and constraints
  • Explore the various options
  • Provide a preferred solution

This benefits your business through providing:

  • An optimal approach to system integration
  • Early identification of problems via targeted integration activities
  • Solutions from a company with a delivery track record
  • Integration of sometimes complex software
  • The ability to work with multiple stakeholders
  • Minimal upfront costs of new systems
  • A diverse range of technical expertise
  • Solutions that match the business need