it's the 21st century: why isn't your data integration loosely coupled?
TRANSCRIPT
It's the 21st Century: Why Isn't Your Data Integration Loosely Coupled?WebinarTuesday, May 19th10:00am PDT / 1:00pm EDT
Today’s Discussion Topics
• Why isn’t your data integration loosely coupled
• SnapLogic introduction and demonstration
• Recommended next steps• Discussion
Copyright © 2015, Intellyx, LLC
3
It’s the 21st Century
Why Isn’t Your Data Integration Loosely Coupled?
Jason BloombergPresident
@theebizwizard
About Jason Bloomberg
• President of Intellyx
• Advise companies on their digital transformation initiatives & help vendors communicate their agility stories
• Write for Forbes & Wired on Digital Transformation
• Buy my latest book, The Agile Architecture Revolution
Copyright © 2015, Intellyx, LLC4
What’s a Connector?
• Programs that know how to interact with an underlying business application
• Performs two-way communication
• Can be specific to an application or class of applications through a standard communication protocol
Copyright © 2015, Intellyx, LLC5
Ph
oto
Cre
dit
: To
m W
ood
ward
htt
ps:
//w
ww
.flic
kr.c
om
/ph
oto
s/b
ion
icte
ach
ing
/
Challenge: Tight Coupling
• Any change in the data format or interface requirements for either end of any interaction would require an update of the connector
• Can also become a single point of failure or a bottleneck that limits scalability
• Introduces brittleness to the application environment
Copyright © 2015, Intellyx, LLC6
A failed interaction may result
Data Integration Limitations
• Traditional connectors may perform data transformations
• Typically require strict, rigid data mapping between endpoints
• Mappings created at design time
Copyright © 2015, Intellyx, LLC7
Ph
oto
Cre
dit
: Lo
ou
is K
. h
ttp
s://
ww
w.fl
ickr
.com
/ph
oto
s/b
on
ap
art
y/
Loose Coupling
• Abstract underlying code with contracted interface
• Separation of concerns between consumers & providers
• Can change underlying code without breaking interaction, as long as endpoints comply with contract
Copyright © 2015, Intellyx, LLC8
Ph
oto
Cre
dit
: R
ay F
ost
er
htt
ps:
//w
ww
.flic
kr.c
om
/ph
oto
s/9
44
18
46
4@
N0
8/9
63
13
93
07
3/s
izes/
c/
SOA to the Rescue?
• Service-Oriented Architecture (SOA) in part intended to resolve limitations of traditional connectors
• By abstracting interfaces to software as Web Services, interactions could now be loosely coupled
Copyright © 2015, Intellyx, LLC9
Ph
oto
Cre
dit
: Th
om
as_
sly h
ttp
s://
ww
w.fl
ickr
.com
/ph
oto
s/to
msl
y/
Loose Coupling with SOA
• Possible to change the underlying software (consumer or provider) without breaking interaction– Both endpoints must
conform to Web Services contract
• Document style contracts include XML Schemas for specifying data formats– Rigid & strongly typed
Copyright © 2015, Intellyx, LLC10
Ph
oto
Cre
dit
: G
ideon
Bu
rton
htt
ps:
//w
ww
.flic
kr.c
om
/ph
oto
s/w
aki
ng
tig
er/
Limitations of Web Services-Based SOA
• Web Services largely fell short in delivering loose coupling
• Web Services still required an underlying software implementation
• Typically became part of the Enterprise Service Bus (ESB)– Traditional piece of integration
middleware exposing connectors – Supported the XML-based Web Services standards– ESBs typically centralized & heavyweight, not
cloud-friendly
Copyright © 2015, Intellyx, LLC11
REST to the Rescue?
• Representational State Transfer (REST)– Architectural style intended to build
hypermedia applications that generalized the behavior of the Web
– Became a lightweight, HTTP-based approach for building application programming interfaces (APIs)
Copyright © 2015, Intellyx, LLC12
Ph
oto
Cre
dit
:
Custom Media Types
• REST loose coupling depends upon Standard Internet Media Types (formerly called MIME types)
• Internet Media Types designed for display metadata– HTML, PDF, etc.
• REST’s answer for custom data formats are Custom Media Types
• Introduce tight coupling– How to communicate, maintain, & version them?
Copyright © 2015, Intellyx, LLC13
Ph
oto
Cre
dit
: P
en
Wag
gen
er
htt
ps:
//w
ww
.flic
kr.c
om
/ph
oto
s/ep
w/4
34
15
54
77
1/s
izes/
z/
The Schemaless Data Trap
• JSON often favored over XML because it is schemaless
• No fixed metadata representing data syntax or semantics
• Problem: interpretation of data falls to underlying logic
Copyright © 2015, Intellyx, LLC14
Another shell game
Ph
oto
Cre
dit
: Van
ess
a D
ualib
htt
ps:
//w
ww
.flic
kr.c
om
/ph
oto
s/re
rin
ha/
Design-Time Introspection
• Schemas and other metadata relevant to the interaction do need not be known before the integration is set up
• SnapLogic Snaps automatically gather such metadata– Automate the
configuration of the integration
Copyright © 2015, Intellyx, LLC15
Ph
oto
Cre
dit
: O
kko P
yykk
ö h
ttp
s://
ww
w.fl
ickr
.com
/ph
oto
s/d
ata
_op
/
Data Integration Dos & Don’ts
• Do:– Plan ahead for horizontal
scalability and fault tolerance (cloud friendliness)
– Favor document-centric data formats
• Don’t:– Use rigid, centralized middleware– Rely heavily on fixed schemas
Copyright © 2015, Intellyx, LLC16
Ph
oto
Cre
dit
: au
dio
-lu
ci-s
tore
.it
htt
ps:
//w
ww
.flic
kr.c
om
/ph
oto
s/au
dio
luci
store
/
Today’s Discussion Topics• Why isn’t your data integration loosely
coupled• SnapLogic introduction and
demonstration• Recommended next steps• Discussion
• Experienced Team: Leadership from Informatica, Salesforce, Sybase, Cognos, CA
• Headquarters: San Mateo, California
• Investors: Andreessen Horowitz & Ignition
• Advisory Board: AstraZeneca, HP, Symantec, Yahoo
• Customers: Adobe, Acxiom, AstraZeneca, Blackberry, Bloomin’ Brands, CapitalOne, Cisco, Cognizant, Danone, Fox Sports, GamesStop, GE, HP, IDG, iRobot, RocketFuel, Target, Yelp, Uber, USF, Xactly
SnapLogic: Unified Platform to
Connect Faster
Why SnapLogic Elastic
Integration?
ModernArchitecture
Connected:300+ Snaps
Productive User Experience
UnifiedPlatform
We can do more in two hours with SnapLogic than we could in two days with traditional
solutions.
SnapLogic Demonstration
Discussion and Next Steps
@SnapLogic Facebook.com/SnapLogic Plus.google.com/+SnapLogic
Learn more atwww.SnapLogic.com
Jason Bloomberg
President, Intellyx
@theebizwizard
Send email NOW to [email protected] to download this presentation
Thank You!
Copyright © 2015, Intellyx, LLC