Hybrid Integration

1. Hybrid Integration
Sep 2017

2. 2Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Agenda
1. Introduction
2. Common Integration Patterns
3. Application Integration Evolution
4. Digital Technologies
5. Key Integrations trends driving digital transformation
6. Why hybrid Integration?
8. Q&A
7. Hybrid Integration Case Study

3. 3Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Introduction
Data Enablement & Integration
Having the right set of data at the right time is key to become successful in today’s digital world. Leveraging business data
can help the clients improve their business intelligence capabilities, take better decisions and gain an edge over their
competitors.
Data Enablement provides the right set of tools and views for creating differentiated customer experience, improving
business processes and winning more opportunities from the market. This is achieved via an integration layer, also known as
middleware layer.
What is an integration?
Integration is a communication system between mutually interacting applications in an enterprise. All the participant
applications can be either a client or a server. The different types of integration architectures are Hub & Spoke and
Enterprise Service Bus.
Why do we need to integrate applications?
The enterprise ecosystem has been complicated as applications, systems and services used by businesses have evolved
over the years. The growing need to connect heterogeneous endpoints in various locations has resulted in businesses
ending up with a divided ecosystem. An integration layer eliminates the challenges and ensure the data spread across
various silos is made available to the business in the right format at the right time.

4. 4Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Common Integration Patterns
Source Target
Move a specific set of data from one system to
the other.
Useful when an application migrates to a newer
version or to a different application. Depending
on need, a transformation is required.
Migration
Source
Target1
Move data from a single source system to
many target systems in an ongoing and
real-time (or near real-time), basis.
Useful when there is a need to keep our
data up-to-date between multiple systems
across time.
Broadcasting
Target2
Source1
View
Combine two datasets in different systems so that they
behave / appear as one, while respecting their need to
exist as different datasets.
Useful when there is a need for representing the reality
to be comprehensive and consistent by consolidating
the data from different systems.
Bi-directional Synchronization
Source2
Source1
View
Identifies the intersection of two data sets and does a bi-directional
synchronization of that scoped dataset only if that item occurs in both
systems naturally.
Useful in the case where there are two groups or systems that want to
share data only if they both have a record representing the same
item/person in reality.
Correlation
Source2
Only acts on the
intersection of two
data sets
Source1
Target
Taking or receiving data from multiple systems and inserting into one.
The aggregation pattern is valuable if you are creating orchestration APIs to
“modernize” legacy systems, especially when you are creating an API which
gets data from multiple systems, and then processes it into one response.
Also useful in scenarios where a common report or dashboard
representation is needed for the data coming from multiple source systems.
Aggregation
Source2

5. 5Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Application Integration Evolution
T H E T R A N S F O R M A T I O N O F
A P P L I C A T I O N I N T E G R A T I O N
App integration processes determine how information flows from one app to another Technologies
like mobility and cloud resulted in new ways data and function can travel
A traditional EAI architecture where
a single integration server, the hub,
handles the information exchange
and transformation for many
applications or data stores, the
spokes. Centralized and less
scalable model of integration.
Buses can serve an enterprise on their
own as an application integration
service, but middleware can too.
Middleware suits can contain bus or
hub-and-spoke (messaging) application
integration tools as well. It can also
contain connectors, to interact with
applications, which minimize the
development efforts
The BUS methods of application
integration allows the data and functions
to travel, and systems to speak to each
other quickly, and without human
interference. This is done through a set
of defined standards that allow any new
application to accept and emit data
provided it fits the standards. One key
aspect of this methods is Guaranteed
delivery.
When it comes to cloud computing,
Microservices are the emerging
standard application architecture.
Microservices, if properly done, fix
potential data traffic jams, by
allowing data to travel to
applications both in the cloud and
on premises.
With Point-to-Point integration the
data goes from one system,
translated and reformatted, then
travels to the next, and then the
next system and so on. While this
route is straightforward, things
quickly get complicated with more
applications and data. The farther
the system, the slower the path.
POINT-TO-POINT INTEGRATION BUS Integration MICROSERVICES
MIDDLEWAREHUB-AND-SPOKE INTEGRATION

6. 6Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Digital Technologies

7. 7Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Key Integration Trends Driving Digital Transformation

8. 8Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Why Hybrid Integration?
• Conversion to an all cloud integration application may not always be the best solution for everyone.
• At the same time, continuing with out-of-date legacy systems is also not an option.
• Hybrid cloud integration provides the perfect balance for enterprises, integrating data from on-premise legacy systems
with cloud data and ensuring that businesses have full advantage when driving forward.
• A hybrid integration platform is securely connected using a technology like Transport Layer Security, so that it supports
the integration of on-premise endpoints, cloud endpoints and the combination of the two, for all integration patterns.
• Transport Layer Security enables connectivity without having to change firewall policies or proxy services.
• Hybrid integration Platform bridges the network divide between your existing enterprise (databases, warehouses,
applications and legacy systems) and SaaS/PaaS, B2B, B2C, BYOD and big data.
• It solves the issue of transferring existing information from on-premise systems and leverages new systems so as to
make way for innovation, competitive advantage and driving new business models.
• The updated enterprise deals with emerging trends in the market, while leveraging the data and functionality of on-
premise legacy applications.
• Hybrid Integration Platform enables on-premise applications to seamlessly integrate with cloud based applications.

9. 9Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Hybrid Integration

10. 10Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Hybrid Integration - Products & Cloud Providers
Integration Products Cloud Providers

11. 11Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Hybrid Integration Case Study – A retail
customer in UK
Mulesoft
VPN
VPN
On - Premise Enterprise Applications
Oracle Financials Mercatus
Enactor
Till Machine 1
Till Machine 2
Till Machine n
Banks
Supplier 1
Supplier 2
Supplier n
Oracle HR
CRM
SACS
Microsoft Azure Cloud
Mulesoft
Enactor Process
Manager
Queue
Queue
VMS
We have implemented a hybrid cloud of one
of our retail customers in UK. This client has multiple
suppliers who suppliers raw material on a sales order and
sends ASN and Invoice transactions. Client sends the
payment information to banks and suppliers. The invoice
and payments information is stored in the oracle
financials. All these transactions pass thru the on –
premise Mulesoft.
There is an other project which implements
hybrid integration for the same client. The Product
information is exchanged between the Enactor process
manager and Mercatus thru the Mulesoft application on
Microsoft Azure cloud. SACS application connects to the
queues on on – premise queues and the on- premise
queues connects to the queues on the cloud via secured
VPN connection to exchange the product information with
Enactor.

12. 12Copyright © Capgemini 2015. All Rights Reserved
Integration Capabilities
Hybrid Integration
Q&A