In this webinar, hear from 451 Research analyst Carl Lehmann about how IT organizations are challenged like never before with several disruptive changes. As hybrid clouds proliferate and as workloads shift across these disruptive venues, enterprises must now consider a thoughtful and strategic approach to hybrid cloud integration. This presentation features a discussion of the business and technical trends driving hybrid cloud integration, how hybrid cloud integration is different from traditional approaches to integration, and why it matters. To learn more, visit: www.snaplogic.com/connect-faster

1. Hybrid Cloud Integration:
Why It's Different and
Why It Matters
Live Webinar
Wednesday, June 17th

2. Today’s Agenda
Carl Lehmann
Research Manager, 451 Research
Erin Curtis
Product Marketing, SnapLogic
• Hybrid Cloud Integration:
Why it’s Different and Why it Matters
• SnapLogic Introduction
• Discussion and Next Steps
Craig Stewart
Product Management, SnapLogic

3. Hybrid Cloud Integration: Why it’s Different
and Why it Matters
Carl Lehmann | 451 Research

4. 451 Research is an information
technology research advisory company
4
Founded in 2000
210+ employees, including over 100 analysts
1,000+ clients: Technology Service providers, corporate
advisory, finance, professional services, and IT decision makers
15,000+ senior IT professionals in our research community
Over 52 million data points each quarter
4,500+ reports published each year covering 2,000+
innovative technology service providers
Headquartered in New York City with offices in London,
Boston, San Francisco, and Washington D.C.
451 Research and its sister company Uptime Institute
comprise the two divisions of The 451 Group
Research Data
Advisory Services
Events

5. 5
Hybrid Cloud Integration: Why it’s Different and Why it Matters
• The business and technical trends driving hybrid cloud integration
• How hybrid cloud integration is different from traditional A2A and B2B
integration, and why it matters
• Cloud integration challenges and how to overcome them
• A reference architecture and best practices for crafting integration strategy
5

6. 6
Hybrid Cloud Integration: Why it’s Different and Why it Matters
• The business and technical trends driving hybrid cloud integration
• How hybrid cloud integration is different from traditional A2A and B2B
integration, and why it matters
• Cloud integration challenges and how to overcome them
• A reference architecture and best practices for crafting integration strategy
6

7. 7
First, integration warrants a baseline definition of hybrid cloud
Hybrid cloud is not…
• Colocation with multiple providers
• Disparate applications running in multiple public clouds
• In these examples the applications and the underlying infrastructure do not interoperate
Hybrid cloud is…
• Simply a delivery model
• It consists of two or more distinct cloud infrastructures and on-premises infrastructure that remain
unique entities, all coordinated by standardized or proprietary technology, and interoperate to
deliver seamless business functions
7

8. Cloud computing projects
Q. What are your organization’s top cloud computing related projects in the next 12 months?
Select up to 3. n=161
8
?
?

9. Spending change for cloud computing 2014 2015 = shifting workloads
9
More
year-­‐over-­‐year
Spending,
Shi2ing
toward
ITaaS
Less
year-­‐over-­‐year
spending

10. The road to hybrid cloud is private
Q. Has your organization configured any of the following clouds for interoperability? n=2002
10

11. 11
Not just clouds, trends driving IT = speed, time to market and quality
• Virtualization
• Software-defined infrastructure (converged and automated)
• Agile application development
• Continues integration/continuous delivery (CI/CD)
• DevOps
• Big data and analytics
• IT-as-a-Service (ITaaS)
• The commoditization of IT
• Mobility
• The ‘API Economy’
• The Internet of Things (IoT)
11
Common
denominators:
data,
applica3ons
and
how
to
integrate
them!

12. All these trends can create silos, the challenge is…
12

13. …how to integrate processes for speed, time to market and quality!
13
SaaS
IaaS
PaaS
Hybrid
On
Premises

14. A key question to ask is…
How
does
all
this
effect
the
way
I
integrate
data
and
applica:ons?
14

15. 15
Hybrid Cloud Integration: Why it’s Different and Why it Matters
• The business and technical trends driving hybrid cloud integration
• How hybrid cloud integration is different from traditional A2A and B2B
integration, and why it matters
• Cloud integration challenges and how to overcome them
• A reference architecture and best practices for crafting integration strategy
15

16. 16
Hybrid cloud integration explained
Hybrid cloud defined
• Hybrid cloud is simply a delivery model – it consists of two or more distinct cloud infrastructures that remain unique entities,
coordinated by standardized or proprietary technology, and interoperate to deliver seamless business functions
What is hybrid cloud integration? (two perspectives)
• Tactical: enables the data and process flows between any number and type of cloud services with any number and type of in-
place IT systems
• Strategic: enables cloud services to be dynamically consumed within IT architecture and exploited on demand for their price/
performance and elasticity advantages
What makes HCI different from traditional A2A and B2B integration?
• Application-to-Application (A2A) deals little with issues beyond the firewall, emphasizes logic and work
• Business-to-Business (B2B) deals little with app logic, emphasizes security and data flow
HCI must deal with both, and…
• Must address data ownership as it transcends boundaries (on-premises, clouds, sovereignty); process orchestration and
GRC (governance, risk and compliance)
• Must help redeploy workloads on-demand to exploit the ‘best execution venue’ (BEV) based on workload profile, policies,
SLA requirements, and process and integration dependencies – without breaking
What is a HCI reference architecture?
• A blueprint of goals, practices, tools and techniques used for data and application integration across clouds
• A framework for assembling the integration technology needed for hybrid IT
16

17. 17
Hybrid Cloud Integration: Why it’s Different and Why it Matters
• The business and technical trends driving hybrid cloud integration
• How hybrid cloud integration is different from traditional A2A and B2B
integration, and why it matters
• Cloud integration challenges and how to overcome them
• A reference architecture and best practices for crafting integration strategy
17

18. 18
Integration challenges and how to overcome them
Integrations must cope with…
• Slow and unreliable networks
• Applications born of different languages, operating environments
• Disparate data formats, quality and transfer techniques
• Change
Integration developers have responded using several basic approaches
• File Transfer
• Used when one app needs to write a file that another application can read
• A Shared Database
• Used when multiple apps need to share a common database and does not need to duplicate data
• Remote Procedure Invocation
• Used when one app needs to expose functionality to another remote app in real-time (synchronous)
• Messaging
• Used when apps need to expose messages (data payload) to a message channel that can be read later by other app
(asynchronous)
• Data management
• Transfer, translate, transform, normalize, enrich, profile, relate context, federate, synchronize, enable big data
18

19. 19
Many integration and data management technologies already in place
Message-oriented middleware (MOM) provides a communications layer to integrate applications
Managed File Transfer (MFT) and File Transfer Protocol (FTP) secure delivery of files that do not need standardization or
transformation
Electronic data interchange (EDI) B2B network exchange of standardized electronic documents
Extract, Transform, Load (ETL) (ELT) extracts data from one system to make it usable to another
Enterprise application integration (EAI) extends MOM with prepackaged connectors used to link to popular application packages
Message Queues (MQs) asynchronous communications, needed when nodes of distributed systems are unavailable due to fault
Message Brokers (MBs) enable message validation, transformation and routing
Enterprise Service Bus (ESB) integrates disparate applications via a communication bus; enables orchestration, transformation,
intelligent routing and mediation
Application Programming Interfaces (APIs) used for A2A and to allow third parties to add value to applications
Data Quality Management (DQM) to improve and verify the reliability and efficiency of data
Master Data Management (MDM) federate, aggregate data to provide a common point of reference
Hadoop to store and process distributed big data
NoSQL for non-relational storage and retrieval of big data
MapReduce for scalability across very large arrays of servers in Hadoop clusters
Not to mention emerging IoT protocols: MQTT, XMPP, DDS, AMQP, CoAP
19
Enabled
via
SW
toolkits,
HW
appliances,
clouds
or
managed
services
All
will
remain,
but
orchestra3on
will
drive
reconfigura3on
based
on
need…

20. 20
Tooling reconfiguration will be based on need: cloud integration waves
First wave addressed on-premises to SaaS data-loading
• Little data quality management
• Accessibly and security entrusted to the SaaS providers
Second wave occurs when…
• SaaS deployments accelerate
• Data quality begins to matter
• Cross-functional processes exchange data among on-premises and SaaS systems (hybrid IT)
• Other applications are offloaded to IaaS and PaaS (workloads shift)
Third wave occurs when…
• Big data becomes a real strategic initiative in an enterprise
• Value can be derived from intelligently managing the Internet of Things (IoT) – operational technology (OT) automation, IT meets OT
Orchestration and control must be addressed to include…
• Central coordination and collaboration of integration designs
• Distributed run-time execution of integrations on-premises and in clouds
• Effective data preparation techniques for ‘total data’ (structured, big, unstructured, batch, synchronous, asynchronous, streaming)
• Coordinated reporting, administration, trouble-shooting and audit control (visibility)
• Data flow and business process orchestration
Will require a cloud strategy and hybrid (multi) cloud integration reference architecture
• A blueprint of goals, methods, practices, tools and techniques
• A framework for design, testing, deployment, measurement and management to all integrations
20

21. 21
Hybrid Cloud Integration: Why it’s Different and Why it Matters
• The business and technical trends driving hybrid cloud integration
• How hybrid cloud integration is different from traditional A2A and B2B
integration, and why it matters
• Cloud integration challenges and how to overcome them
• A reference architecture and best practices for crafting integration strategy
21

22. A hybrid multi-cloud integration reference architecture (common today)
Internet
Hosted,
Managed
Services
Private
Cloud(s)
Security
Strategy/Stack
MulC-­‐Clouds
Start/End
points
Security-­‐as-­‐a-­‐
Service
ConnecCvity
Services,
WAN/VPN
API
Services
IntegraCon
Process
Data
Systems
of
Record
Databases
Metadata
Repositories
Services
Repositories
iPaaS(s)
Systems
of
Engagement
(ApplicaCons),
Business
Logic,
Mashups,
Social
Business
PaaS/IaaS
SaaS(s)
Firewall
/
DMZ
/
Secure
Gateways
Process
OrchestraCon
(Dataflow,
Workflow),
Event
Management
Data
Hub,
Big
Data
(Hadoop,
NoSQL),
MDM,
Quality
Mgmt.,
TranslaCon,
TransformaCon,
Enrichment
Enterprise
Service
Bus
(ESB)
API
Portal/
Gateway
ConnecCvity,
Networks
and
Network
Management
Source:
Carl
F.
Lehmann
carl.lehmann@451research.com
Message
Queuing
iPaaS
Design
Browsers
PCs,
Tablets
B2B
Phones
Governance
(Rules,
Policies)
User
Services
Core
components
• Process
orchestraCon
components
enable
control
of
events,
data
and
workflows
• IntegraCon
components
provide
synchronous
and
asynchronous
connecCvity
for
batch,
real-­‐
Cme
and
streaming
data
flows
–
internal
and
external
to
the
enterprise
• Data
management
components
manage
the
quality,
purpose
and
use
of
data
from
capture
through
consumpCon
Deploy
technologies
needed
for:
• ApplicaCon-­‐to-­‐ApplicaCon
(A2A)
• Business-­‐to-­‐Business
(B2B)
• ApplicaCon-­‐to-­‐Cloud
(A2C)
• Cloud-­‐to-­‐Cloud
(C2C)
• Variants
as
needed
of
A2B2C
22
Self
Service
Catalogs,
AppStore,
Provisioning
IdenCty
Access
Mgmt.,
SSO
Hybrid
Cloud
Components
ETL

23. 23
But remember – trends driving IT = speed, time to market and quality
• Virtualization
• Software-defined infrastructure (converged and automated)
• Agile application development
• Continues integration/continuous delivery (CI/CD)
• DevOps
• Big data and analytics
• IT-as-a-Service (ITaaS)
• The commoditization of IT
• Mobility
• The ‘API Economy’
• The Internet of Things (IoT)
23
Common
denominators:
data,
applicaCons
and
how
to
integrate
them
Will
drive
the
HCI
reference
architecture
to
reconfigure
and
converge…

24. A hybrid multi-cloud integration reference architecture (to support IT trends)
24
Internet
Hybrid
Mul3-­‐Cloud
Integra3on
Reference
Architecture
Hosted,
Managed
Services
Private
Cloud(s)
Security
Strategy/Stack
MulC-­‐Clouds
Start/End
points
Security-­‐as-­‐a-­‐
Service
ConnecCvity
Services,
WAN/VPN
API
Services
Systems
of
Record
Databases
Metadata
Repositories
Services
Repositories
iPaaS(s)
Systems
of
Engagement
(ApplicaCons),
Business
Logic,
Mashups,
Social
Business
PaaS/IaaS
SaaS(s)
Firewall
/
DMZ
/
Secure
Gateways
Process
Orchestra3on
(Dataflow,
Workflow),
Event
Management
Data
Hub,
Big
Data
(Hadoop,
NoSQL)
,
MDM,
Quality
Mgmt.,
Transla3on,
Transforma3on,
Enrichment
ConnecCvity,
Networks
and
Network
Management
Source:
Carl
F.
Lehmann
carl.lehmann@451research.com
Browsers
PCs,
Tablets
B2B
Phones
Governance
(Rules,
Policies)
User
Services
Hybrid
Mul3-­‐Cloud
Services
Self
Service
Catalogs,
AppStore,
Provisioning
IdenCty
Access
Mgmt.,
SSO
Enterprise
Service
Bus
(ESB),
Message
Queuing,
ETL,
iPaaS
Design
Management,
API
Management,
IoT
Integra3on
Services
Process
Services
Data
Services
Ø Technology
prolifera3on
will
drive
users
to
consolidate
vendors
Ø The
pursuit
of
subs3tu3ons
that
consolidate
func3ons
will
increase
Ø The
ability
to
redeploy
to
BEV
on
either
side
of
the
firewall
will
be
sought
Converged
capabiliCes
• Process
services
enable
orchestraCon
of
events,
data
and
workflows
• IntegraCon
services
provide
synchronous
and
asynchronous
connecCvity
for
batch,
real-­‐Cme
and
streaming
data
flows
–
internal
and
external
to
the
enterprise
• Data
services
manage
the
quality,
purpose
and
use
of
data
from
capture
through
consumpCon
Configure
paberns
and
templates
for:
• ApplicaCon-­‐to-­‐ApplicaCon
(A2A)
• Business-­‐to-­‐Business
(B2B)
• ApplicaCon-­‐to-­‐Cloud
(A2C)
• Cloud-­‐to-­‐Cloud
(C2C)
• Variants
as
needed
of
A2B2C
Devices,
Things

25. 25
Best practices for hybrid cloud integration
Craft a cloud strategy
• Goals, methods, practices, tools and techniques
• Under what conditions, do what workloads shift, to what execution venue?
• Plan to streamline cross-functional processes across cloud and on premise venues to minimize
complexity and integration execution overhead
• Craft rules for private vs. public cloud use (cloudbursting ‘elasticity’ strategy)
Define a hybrid multi-cloud integration reference architecture
• Use it to manage integration strategy and proactively plan for changing business and technology
needs
Seek platforms that unify data and application integration functions
• To simplify tooling and enable consistency for development, execution and management
• To enable the second wave of cloud integration (expanded private cloud, hybrid IT and ITaaS)
• To support the third wave of cloud integration (actionable intelligence from big data)
25

26. Thank You!
carl.lehmann@451research.com

27. SnapLogic: Unified Platform to Connect Faster
Our unified platform significantly speeds up enterprise data access everywhere.
– Gaurav Dhillon, co-founder and CEO, SnapLogic

28. Why SnapLogic Elastic Integration?
Modern
Architecture
Connected:
300+ Snaps
Productive UX
Unified
Platform

29. Productive: UX for Citizen and Advanced Users
We can do more in two hours with
SnapLogic than we could in two days
with traditional solutions.
• Integration Cloud: Design, Admin, Monitoring
• Drag, Drop, Connect HTML5 interface built for speed

30. A SnapLogic Pipeline
Bulk Upload, Compression, Parallelism without any custom code/scripts

31. Modern Architecture: Hybrid and Elastic
Streams: No data is
stored/cached
Secure: 100%
standards-based
Elastic: Scales out
handles data and app
integration use cases
Metadata
Data
Databases Enterprise Systems Hadoop

32. Modern Architecture: Real-Time and Batch
Ultra Pipelines SnapReduce and the Hadooplex
Map Reduce
Certified YARN Execution

33. Connected: 300+ Snaps
We look at SnapLogic as an opportunity to
think differently about integration.

34. Common SnapLogic Use Cases
Cloud App
Integration
• Workday: HR On-
Boarding
• Salesforce: CRM Back
Office
• Eliminate SaaS Silos
Digital
Marketing
• AWS Redshift
• Tableau, Social, CRM
• Cloud Analytics
Big Data
Analytics
Enterprise
Platform
• Data Ingestion
• Data Preparation
• Data Delivery
• Self Service
• Data, Apps, APIs
• Integrator’s Solution

35. SnapLogic Customer Success

36. Discussion and Next Steps
@SnapLogic
Facebook.com/SnapLogic
Carl Lehmann
Research Manager, 451 Research
See SnapLogic
in action:
Contact us: info@snaplogic.com
http://video.snaplogic.com/