More Related Content Similar to Webinar: It's the 21st Century - Why Isn't Your Data Integration Loosely Coupled? (20) Webinar: It's the 21st Century - Why Isn't Your Data Integration Loosely Coupled?1. It's the 21st Century:
Why Isn'tYour Data Integration
Loosely Coupled?
Webinar
Tuesday, May 19th
10:00am PDT / 1:00pm EDT
2. Today’s Discussion Topics
• Why isn’t your data integration loosely coupled
• SnapLogic introduction and demonstration
• Recommended next steps
• Discussion
3. Copyright © 2015, Intellyx, LLC
3
It’s the 21st Century
Why Isn’t Your Data Integration
Loosely Coupled?
Jason Bloomberg
President
jason@intellyx.com
@theebizwizard
4. 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
5. 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
PhotoCredit:TomWoodwardhttps://www.flickr.com/photos/bionicteaching/
6. 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
7. 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
PhotoCredit:LoouisK.https://www.flickr.com/photos/bonaparty/
8. 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
PhotoCredit:RayFosterhttps://www.flickr.com/photos/94418464@N08/9631393073/sizes/c/
9. 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
PhotoCredit:Thomas_slyhttps://www.flickr.com/photos/tomsly/
10. 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
PhotoCredit:GideonBurtonhttps://www.flickr.com/photos/wakingtiger/
11. 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
12. 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
PhotoCredit:
13. 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
PhotoCredit:PenWaggenerhttps://www.flickr.com/photos/epw/4341554771/sizes/z/
14. 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
PhotoCredit:VanessaDualibhttps://www.flickr.com/photos/rerinha/
15. 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
PhotoCredit:OkkoPyykköhttps://www.flickr.com/photos/data_op/
16. 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
PhotoCredit:audio-luci-store.ithttps://www.flickr.com/photos/audiolucistore/
17. Today’s Discussion Topics
• Why isn’t your data integration loosely coupled
• SnapLogic introduction and demonstration
• Recommended next steps
• Discussion
18. • 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
19. Why SnapLogic Elastic Integration?
Modern
Architecture
Connected:
300+ Snaps
Productive
User Experience
Unified
Platform
We can do more in two hours with SnapLogic than we
could in two days with traditional solutions.
21. Discussion and Next Steps
@SnapLogic
Facebook.com/SnapLogic
Plus.google.com/+SnapLogic
Learn more at!
www.SnapLogic.com!
!