Four Critical iPaaS Requirements That You Can Ignore Only At Your Own Peril
7
1 Four Critical iPaaS Requirements That You Can Ignore Only At Your Own Peril Maneesh Joshi Senior Director of Product Marketing and Strategy SnapLogic
-
Upload
snaplogic-inc -
Category
Technology
-
view
678 -
download
0
description
These slides supplement a blog series that reviews classic integration requirements and outlines four new requirements that are driving the demand for cloud integration in the enterprise. The four new requirements are: 1. Resiliency to changes 2. Fluidity in hybrid deployments 3. Non-existent lifecycle management of the platform 4. A modern platform for SMACT To learn more, visit: http://www.snaplogic.com/blog.
Transcript of Four Critical iPaaS Requirements That You Can Ignore Only At Your Own Peril
1
Four Critical iPaaS Requirements That You Can Ignore Only At Your Own Peril
Maneesh JoshiSenior Director of Product Marketing and StrategySnapLogic
2
The Integration Platform Check List
Year 2009
Metadata-driven
Drag and drop
Pre-built connectors
Management & Monitoring
Transactional support
SOAP and REST APIs
Transformation
Cloud deployment
Year 2014
Metadata-driven
Drag and drop
Pre-built connectors
Management & Monitoring
Transactional support
SOAP and REST APIs
Transformation
Cloud deployment
Resiliency
Hybrid architecture fluidity
Lifecycle management
Social, mobile, analytics, cloud, and IoT (SMACT)
3
#1 Resiliency To Changes
Schema changes
API changes
New data field requirements
Loose coupling
Late binding
Smart linking
Every little change doesn’t break integrations
Reduces rework
Makes the hub and spoke architecture possible without enforcing a canonical schema
PainPoints
PlatformExpectations
Why You Should Care
4
#2 Hybrid Architecture Fluidity
Apps move
Data source changes
Data gravity shifts
Multiple dashboards
Firewall holes
Deployment flexibility
Integrations shouldn’t break
Single dashboard for entire infrastructure
Standard HTTP and HTTPS
Responding to app and data source changes is expensive and causes critical delays
Impacts business agility
Dual management and monitoring of a distributed deployment is a nightmare
PainPoints
PlatformExpectations
Why You Should Care
5
#3 Lifecycle Management of Integrations
New software versions
New connectors
Management of configurations and customizations in distributed environments
Self-upgrading cloud
and on-premise software
Global configurations
Automatic management of customizations
No IDEs
Always stay current with vendor innovation
No costly downtimes for patch application
No costly downtimes to upgrade configurations and customizations
PainPoints
PlatformExpectations
Why You Should Care
$
$ $
6
#4 Modern Platform for SMACT
ETL vs. EAI dilemma
Social data
Mobile-enabling of apps
Exploding IoT and log data volumes
Elastic scale
Lightweight JSON (not XML)
Native REST support
Data streaming capabilities
No need for two platforms – one EAI and one ETL
Fewer skilled resources, lower licensing costs
Limited capacity planning for integration projects
Compact JSON means higher performance, lower hardware requirements, and mobile-ready applications
No mobile middleware necessary
PainPoints
PlatformExpectations
Why You Should Care
7
Learn more…
Download the white paper at:
www.SnapLogic.com/dilemma
And try out the SnapLogic Free Trial for Amazon Redshift:
www.SnapLogic.com/Redshift-Trial
