Cloud Integration Strategy

National Capital Oracle Users Group
Tuesday, February 4, 2020 | 6:00pm
Reston Regional Library | Meeting Room 1
Cloud Integration Strategy

© Revelation Technologies Group, Inc. 2020 | All rights reserved. Slide 2 of 20
@Revelation_Tech
Agenda
1. About Me
2. Integration Approaches
o Point-to-Point
o On-Prem Integration Platform
o Cloud Integration Platform (PaaS)
o Enterprise iPaaS
3. Final Thoughts

@Revelation_Tech
About Me
• 20+ years of IT experience
• M.S. in Computer Science from George Mason University
• Past employment with Booz Allen Hamilton, IBM, CSC, and Oracle
• Federal IT projects for the DOD, DHS, DOJ, and DOE
• Recent emphasis on DevOps, cloud, and security in current projects
• Oracle ACE, OCE, OCA
• Author, Presenter, Blogger
• @Ahmed_Aboulnaga

@Revelation_Tech
Typical Integration Development Lifecycle
DESIGN
▪ Review Ariba APIs
▪ Functional design
▪ Technical design
DEVELOPMENT
▪ Integrated SOA
Gateway setup
▪ Web service
development
COMMON
UTILITIES
▪ Exception handling
▪ Message retries
▪ Message recovery
▪ Auditing
SECURITY
▪ Authentication
▪ WS-Security
▪ Transport security
▪ Encryption
RUNTIME
▪ SLA management
▪ Threat protection
▪ QoS monitoring
▪ Analytics and usage
Integrated
SOA
Gateway
CATALOG
▪ Catalog services
▪ Documentation
▪ Reusability

@Revelation_Tech
Integration Platform Strategies Point-to-Point
Integration
Platform
PaaS
iPaaS
On-Prem Integration Platform
Cloud Integration Platform (PaaS)
Enterprise iPaaS
Point-to-Point
▪ Quickest implementation
▪ Worst strategy
▪ Results in repetition of effort for future cloud integration
projects
On-Prem Integration Platform
▪ Involves additional integration development cost/effort
▪ Can establish standards and reusability for future cloud
integrations
Cloud Integration Platform (PaaS)
▪ Same as above except hosted on vendor cloud
Enterprise iPaaS
▪ Next generation integration approach
▪ Great for standard integrations due to readily available
connectors
▪ Not yet as mature compared to traditional SOA platforms
▪ Requirements not out-of-the-box will pose challenges

@Revelation_Tech
#1: Point-to-Point Considerations
• Avoid repetition of effort for future cloud integration
projects since a considerable effort will be spent “getting
it right” the first time.
Cloud Integration
Considerations
▪ End-to-end security
▪ Monitoring
▪ SLA management
▪ Publish reusable APIs
▪ Logging
▪ Auditing
▪ Exception handling
▪ Guaranteed delivery
▪ Inbound architecture

@Revelation_Tech
#2: Leverage an On-Prem Integration Platform
• Consider Oracle SOA Suite, a complete, standards-based, best-of-breed,
unified application integration platform.
Integration
Platform
security
business logic
common error handling
common auditing
common retries

@Revelation_Tech
Point-to-Point vs. SOA
Data Warehouse
Web App
Mainframe
Payment
Provider
Data Warehouse
Web App
Mainframe
Payment
Provider
SOA

@Revelation_Tech
API Gateway
• An API Gateway is necessary for any inbound requests.
• It provides all necessary security, threat protection, SLA management, analytics,
and monitoring.
Integration
Layer
security
monitoring
protection – DoS, throttling, etc.
Gateway

@Revelation_Tech
API Catalog
• Publish and document APIs for reusability.
• For EBS developers, similar in concept to the Integration Repository.
Integration
Platform
service catalog – for documentation and reusability
API
Catalog

@Revelation_Tech
API Catalog Screenshots
Oracle API Catalog Cloud Service

@Revelation_Tech
Challenges of Integration with Cloud Services
• Little web service and security standardization among SaaS providers.
• Development requires a lot of unique communication to SaaS APIs.
• Bi-directional data synchronization complexities.
significant amount of coding

@Revelation_Tech
The Zapier Example
• Zapier has connectors for over 1,500 apps.
• Zapier is an iPaaS geared towards the individual consumer market.
• Easy integration.

@Revelation_Tech
The Zapier Example

@Revelation_Tech
The Celigo Example

@Revelation_Tech
#3: Enterprise iPaaS
• Adapters and connectors are readily available
(and continues to mature).
• Easier integration and less development.
• Limited customization.
• Many product vendors to choose from.
• Must conduct analysis and review for product
selection.
• Still a maturing field, but is the future direction
for cloud integrations.
• Proceed with some caution.
Magic Quadrant for Enterprise Integration Platform as a Service

@Revelation_Tech
SaaS Connector Example from Oracle
• Connectors are readily available, minimizing/simplifying development.

@Revelation_Tech
Enterprise iPaaS Considerations
• Are connectors/adapters/recipes available?
• Do they support the functional requirements?
• Are you okay with limited customization?
SaaS Application Adapters
Featured Applications
On-Premises Application Adapters
What do you want to connect?
Connector Wizards
Connector Recipes

@Revelation_Tech
Final Thoughts
• Each SaaS vendor has its own methods for security and interfacing.
• Accept a hybrid IT architecture.
• Establish practical on-prem/cloud coexistence scenarios.
• Abstract your services whenever possible.

@Revelation_Tech
biggest factor contributing to failure
Next Steps
• Establish an integration strategy.
• Independently assess approach and market products.
• Buy, build, or partner? Consider skills, product maturity, and cost.
• Design and develop common services ahead of time.
• Don’t over architect.

Cloud Integration Strategy

More Related Content

What's hot

Similar to Cloud Integration Strategy

More from Revelation Technologies

Recently uploaded

Cloud Integration Strategy