SaaS is all around. It does not change integration needs, but makes you face new challenges. In this presentation, you will discover the impact of SaaS on cloud integration.

1. The rise of SaaS.
What is its impact on
Cloud Integration?
Sam Vanhoutte
@samvanhoutte

2. Source: Gartner (August 2014)
The Gartner hype cycle

3. 3
Software as a Service

4. Integration needs

5. Integration needs don’t change
5
Loyalty Travel CRM Health
Campaign CRM LOB ERP HR
Time
Card
Benefits
BI
Portal
BI Shop

6. Integration needs don’t change
6
Health
Campaign CRM LOB ERP HR
Time
Card
Benefits
Cloud
CRM
Loyalty Travel
BI
Portal
BI Shop

7. Integration needs don’t change
➔ B2B integration
➔ Business process & Workflow
➔ Data synchronization (replication)
➔ Front-end enrichment (lookup)
➔ Reusability
7

8. Patterns
Cloud-to-ground
Cloud-initiated integration
pattern. Important to
reach on-prem application
in a secure and managed
manner.
Ground-to-cloud
On-prem application
initiates the integration in
an outbound direction.
This is traditional and
common to set up.
Cloud-to-cloud
Integration processes in
the public space. From
one cloud application to
another.

9. Choosing the right exchange pattern
9
RPC Async
Information lookup
SOA approach
Avoid data duplication
UI integration
Durable messaging
Scalable & multi-cast
Standards based
Temporary unavailable
Bulk
Scheduled data exchange
Bulk or batch data
Traditional apps
Initial import & data load

10. Integration challenges…
...and how to tackle them

11. External Connectivity
11
DMZ vs
new approach Firewall setup Identity Protocols
➔ Service Bus relay capabilities (RPC style)
➔ Messaging standards, like AMQP
➔ Single Sign On capabilities (Active Directory or Federation)

12. DevOps
12
More
self-service
Security &
RBAC
Staging &
ALM
External
connections
➔ Align procedures
➔ Good communication between Dev & Ops
➔ Automation of ALM

13. Network dependencies
13
Blocking
Request-reply
Network
reliability
Network
latency
Disaster
recovery
➔ Implement the right retry patterns for the right integration
➔ Avoid blocking request-reply calls, prefer Async at all time
➔ Review chatty architectures of existing applications
➔ Leverage fail-over capabilities of cloud platforms

14. Fast iterations in the cloud
14
New services New features
Backwards
compatibility
Deprecation of
services
➔ Closely follow up on roadmap & announcements
➔ Design for change
➔ Use abstraction to cope with changes
➔ Foresee versioning or compatibility for external API

15. Security & identity
15
Security
dependencies
A lot of
standards
Single Sign-On
needs
Identity
mapping
➔ Verify security approach of your cloud vendors
➔ Handle security on the edge, supporting several endpoints
➔ Leverage Azure Active Directory single sign on

16. Visibility & management
16
Every SaaS has
monitoring Correlation Management
Configuration
settings
➔ Opt for centralized monitoring
➔ Extract metadata
➔ Automate configuration management

17. Mobility
17
API
management
Lightweight
data transfer Device security
Public vs
private users
➔ Monitor usage of API’s and versions
➔ Reconsider chatty or heavy communications
➔ Avoid storing data on device

18. Cloud Integration
Approach

19. The architectures
Traditional on-premise
hub
19
Cloud
Hybrid
integration hub approach
Point-to-point

20. On premise integration platform
➔ Continue existing investments
➔ Existing / traditional integration software gets cloud-enabled
➔ BizTalk Server cloud enabled through Service Bus
➔ REST-support added
➔ Messaging supported
➔ Centralized monitoring
Traditional on-premise
20
hub

21. Sample scenario
Advantages
• Faster set-up of partner connections
• One-time firewall set-up
• Support for existing mappings & schemas in MABS
• No specific DMZ deployment needed
SaaS application
REST call
Reasoning
• Latency less important for B2B than EAI BizTalk ESB
Service Bus Relay
SAP WMS Oracle

22. Cloud-based integration platforms
➔ Integration as a Service, auto-upgrade
➔ iPAAS (integration platform as a service)
➔ Enabling new scenarios (light-weight integration)
➔ Ideal for SaaS integration
➔ New pricing models (pay per use…)
➔ Solution oriented
Cloud
integration hub
22

23. Sample scenario
➔ Integration as a Service
➔ Low-cost integration
➔ Firewall friendly
Relay connections
➔ No DMZ needed
➔ Configuration from the
cloud
➔ Centralized monitoring
23
BizTalk
Adapter
Service
France
Codit Integration Cloud
Azure BizTalk Services
Service Bus Relay
Connector
SQL REST FILE
Cloud
Canada

24. Hybrid integration platform
➔ Best of both worlds
➔ On premise for EAI
➔ Lowest latency
➔ No internet dependency
➔ Cloud for B2B & SaaS
➔ Monitoring challenges
24
Hybrid
approach

25. Sample scenario
Advantages
• Faster set-up of partner connections
• One-time firewall set-up
• Support for existing mappings & schemas in MABS
• No specific DMZ deployment needed
Reasoning
• Latency less important for B2B than EAI
BizTalk Services
Integration Cloud
BizTalk ESB
Service Bus Relay
SAP WMS Oracle
FTP, AS2…

26. Summary
 SaaS will drive cloud integration
 Consider the specificities of cloud
integration, when designing
 Pick the right platform

27. Looking forward to hearing from you
Sam VANHOUTTE
CTO
7 year - BizTalk V-TSP
1st year - Integration MVP
sales@codit.eu
@SamVanhoutte
be.linkedin.com/in/samvanhoutte/
> 60 Active integration customers
International Focus -
Focused on integration solutions HQ in BE
2000 Belgium
2004 France
2013 Portugal
60 employees
e-news + SoMe > 50 consultants BizTalk certified
2012 & 2013
Partner of the Year
Award Finalist
Application Integration