Cloud-native Integration in the Oracle Cloud

© OPITZ CONSULTING 2020
Informationsklassifikation:
Interner Gebrauch
¢¢¢ Digitale Service Manufaktur
Sven Bernhardt, Chief Architect / Integration
Evangelist
Cloud-native Integration
solutions with Oracle
Cloud

Interner GebrauchCloud-native Integration solutions
That’s me
Sven Bernhardt
Cloud-Native enthusiast, API & integration geek. Always curious how new
technologies and concepts can help to make things more valuable and
efficient.
Proud father of a son, passionate football/soccer fan and player. Loves
listening to good hand-made music (Heavy Metal).
¢ Chief Architect / Integration Evangelist
@OPITZ CONSULTING Deutschland GmbH
¢ Oracle ACE Director
@sbernhardt
https://svenbernhardt.wordpress.com/

Interner Gebrauch Seite 3
Agenda
1
2
3
4
5
Vision
Integration today
Architectural considerations
Integration in the Oracle Cloud
Summary
Cloud-native Integration solutions

Vision
1

Ensure that data is where it is needed when it is needed
in the form in which it is needed
System
A
System
B

Integration is key to modernize the business and
establish new business models
¢ From projects to product-centric application delivery model
¢ Product delivers continuous value
¢ Value drives investements
¢ Team is responsible for a specific product as long as product lives
¢ Integration solutions helps to
¢ Further innovation
¢ Dissolve data silos and consolidate data
¢ Adapt new technologies and concepts (like AI / ML)
¢ Integrate the new digital world and legacy systems

Interner Gebrauch
Standard(On-
Prem)
DigitalProduct
Monolith
DigitalProduct
Business Domain
Shared Application Platform
Shared Services (Foundation)
Hybrid, flexible Infrastructure
Standard(On-
Prem)
StandardSaaS
Business DomainBusiness Domain
Digital Product
Business-driven product-centric application world

Integration today
2

Status quo: Integration solutions are usually built upon a
monolithic middleware solution
Source A Sink A
Source B Sink B
Source C Sink C
Client A Client B Client C
Middleware Platform

ESB platforms as technology to address integration
concerns
¢ SOA-style application architectures
¢ Interoperability
¢ Standard-based interfaces
¢ Loose coupling (semi-decoupled services)
¢ Reusable components / services
¢ Canonical data model
¢ System-2-System Integration
¢ Based on Patterns
Application Logic
Integration Logic
Infrastructure
ESB
Service Service Service
Service Service Service
Source: https://tinyurl.com/yyqn6l3x
Rethink!

New technologies and concepts require rethinking about
how integration solutions should be build today

Challenges of integration solutions today
¢ Monolithic / aging systems
¢ Disparate data models
¢ Architectural complexity
¢ Heterogeneous ecosystem
¢ Technical debt
¢ Bloated projects / overhead
¢ Visibility / error handling
¢ Production deployment
Source: Lucas Jellema, https://tinyurl.com/y6h2yf25

Integration is complex because it addresses complex
problems
¢ Miscellaneous communication protocols
¢ Different data serialization formats
¢ Different data structure and unclear semantics
¢ Uneven distribution of data volumes
¢ Different non-functional pre-requisites of systems to integrate
¢ Availability
¢ Processing-Performance / Responsiveness
¢ Max. # of parallel processes
¢ …
¢ Data Privacy and security

Interner Gebrauch
Enterprise Integration challenges are multi-dimensional:
horizontal or vertical either on-premise or in the cloud
Horizontale Integration
VertikaleIntegration

Cloud enables new opportunities, but introduce
additional complexity: Hybrid integration scenarios

Architectural considerations
3

Requirements to modern integration solutions
¢ Less expert knowledge to implement integration requirements (make
integration more mass compatible)
¢ Flexibility in choosing a proper state-of-the-art technology
¢ Address dynamic workloads
¢ (Nearly) Unlimited scalability per integration
¢ Efficient resource consumption

Postulates for building sustainable, flexible integration
solutions
¢ The world is hybrid
¢ Multi-cloud will be the rule, not the exception
¢ Applications adhere to Cloud-native principles
¢ Security by design
¢ Integration requirements differ depending on the direction
¢ Horizontal direction: Asynchronous Event-based Integration (X-Domain)
¢ Vertical direction: Synchronous API-led Integration
¢ Applications have well-defined, intuitive APIs (API design-first)
¢ System integration and data integration are no longer disjoint disciplines

Solution Strategy
¢ Key elements of modern integration solutions:
¢ API Gateway & API Management Tools (API Portal, API pages, API usage monitoring, etc.)
¢ Event Hub
¢ Lightweight ESB solution
¢ iPaaS (Cloud) for SaaS integrations
¢ To be able to comprehensible understand what’s going on within the
distributed integration implementations, Observability is key
¢ Logging
¢ Metrics
¢ Tracing
¢ Centralized, transparent error management is key for sustainable
integration implementation

The way integration solutions should be built nowadays
Source A Sink A
Integr
ation
1
Integr
ation
2
Source B Sink B
Source C Sink C
Event Hub
API Exposure
Client A Client B Client C
f()
f()
f()
Containers Functions
Application Logic
Integration Logic

Integration architecture components in the Oracle Cloud
Platform
API exposure
API Gateway
(OCI API Gateway)
Service
implementation
Cloud-native
Adapter
(Apache Camel)
IAM
Oracle Identity and
Access Management
(IAM)
Metrics visualisation
(OCI Monitoring)
Log Management
(OCI Logging)
Persistence
Credential
Management
(OCI Vault)
Container Orchestration
(OCI Container Engine for
Kubernetes)
Event Hub
(OCI Streaming)
Node/Host
Monitoring
(OCI Monitoring)
Lightweight ESB
(Apache Camel)
Monitoring Database
(OCI Monitoring)
Log Database
(OCI Logging)
iPaaS
(Oracle Integration Cloud)
Error Handler
(Helidon)
SaaS Adapter
(Oracle Integration
Cloud)
Service Discovery
(OCI Container
Engine for
Kubernetes)
Relational Database
(Oracle Database)
Service Monitoring
(OCI Monitoring)
API Threat Protection
(OCI WAF)

Evolution of application infrastructures: From on-
premises to hybrid, scalable and elastic infrastructures
¢ Kubernetes is the new de-facto
application platform
¢ Container orchestration platform
developed by Google
¢ Abstracts Infrastructure, Network &
Storage
¢ Cloud technologies enable infinite
scalability and elasticity on a
infrastructure level

Integration in the Oracle Cloud
4

Remember: Integration is multi-dimensional and
complex
¢ API-led integration
¢ Event-based integration
¢ X-Domain integration
¢ Inter-Domain integration
¢ Closed Apps/COTS integration
¢ Data Ingestion (Change Data Capture)
¢ SaaS integration

Vertical / API-led integration
¢ Important to product-oriented organization
¢ Consider the audience of your API (User-centric API desgin)
¢ Apply suitable solution strategy and governance to the different API types
¢ Use optimized protocols and marshalling techniques for domain-
internal API calls (gRPC)
¢ API Gateway should support a flexible deployment model; ideally
supports hybrid deployment

Interner Gebrauch
API Exposure
Vertical / API-led integration
Consumer 1 Consumer 2 Consumer 3
CN Svc
11 f()
Application Logic
Integration Logic
¢ OCI services of interest:
¢ WAF
¢ API Gateway
¢ OKE / OCIR
¢ Functions
¢ Important patterns:
¢ API Gateway
¢ Backend-for-Frontend (BFF)
¢ API Composition
¢ Routing
Domain 1
Domain 2
Domain 3
CN Svc
12
f()
f()CN
Svc
22
CN
Svc
23
CN
Svc
21
[HTTPS] [HTTPS] [HTTPS]
[gRPC][gRPC]

Horizontal integration
¢ For X-domain communication services use domain events
¢ For Inter-domain communication use optimized protocols at least
¢ If not possible: reconsider the domain decomposition (and / or the user
interface)
¢ Events definitions are first-class citizens
¢ Should be defined using an industry-proven Interface Definition Language (IDL)
¢ Async API
¢ AVRO
¢ Protobuf
¢ Event design-first approach
¢ Event definitions need proper governance

Horizontal integration
Application Logic
Integration Logic
¢ OKE / OCIR
¢ Streaming
¢ Event Sourcing
¢ CQRS
¢ Publish / Subscribe
¢ Service Mesh
¢ Routing
CN Svc
11
Domain 1
Domain 2
CN Svc
12
CN
Svc
22
CN
Svc
23
Event Hub
Proxy
Proxy

Closed Apps / COTS integration
¢ Implemented using lightweight ESB implementations
¢ Lightweight ESB offers Adapter implementations for common COTS
systems
¢ Main points to consider:
¢ Provide connectivity to Legacy/COTS apps
¢ Service virtualization
¢ Protocol transformation (Proprietary -> Standard-based)
¢ Data format transformation

Interner Gebrauch
API Exposure
Closed Apps / COTS integration Consumer 1
Application Logic
Integration Logic
COTS 1
¢ WAF
¢ API Gateway
¢ OKE
¢ Functions
¢ Streaming
¢ Event Sourcing
¢ CQRS
¢ Routing
Domain 1
Domain 2
Domain 3
COTS 2
CN
Svc
21
CN
Svc
31
Event Hub
f()

Data ingestion (Change Data Capture)
¢ Specific case of data integration (one-way)
¢ Moving massive amounts of data
¢ May involve data format transformation
¢ May include
¢ ETL
¢ Streaming (e.g. IoT)
¢ CDC

Data ingestion
¢ Oracle Database (e.g. ATP)
¢ Oracle GoldenGate
¢ OKE
¢ Functions
¢ (Streaming)
¢ Event Sourcing
¢ CQRS
Oracle Golden
Gate CS Event Hub
COTS 1
CN
Svc
21
CN Svc
11

SaaS Integration
¢ Two main integration scenarios to consider:
¢ Cloud-2-Cloud integration (e.g. Workday to Salesforce CRM)
¢ Cloud-2-On-prem integration (e.g. Salesforce CRM to SAP)
¢ External inbound connections (Cloud-2-On-prem) always goes through the
API Gateway
¢ Access to on-prem Legacy/COTS apps always using lightweight ESB
¢ Oracle Integration Cloud (OIC)
¢ VPN / FastConnect (Secure Cloud to On-prem communication)

SaaS Integration SaaS 2SaaS 1
Integration Platform
as a Service (IPaaS)
Service
Application Logic
Integration Logic
ServiceService
API Exposure
CN
Svc
11
Dom
ain
1
CN
Svc
21
Dom
ain
2
COTS 1
Event Hub
Service
CN
Svc
12
¢ Oracle Integration Cloud (OIC)
¢ Routing
¢ Transformation

Summary
5

Not everything we’ve done so far in the integration
space was bad!
¢ Rethink what we did so far and
checkout new opportunities
¢ Being agile and flexible is key to be
successful
¢ Coexistence instead of displacement;
combine “old” and “new” world
¢ Technology and concepts are evolving
but integration patterns stay the same

Integration is more relevant than ever in this hybrid,
Multi-Cloud world!
¢ Integration scenarios are increasingly complex because of:
¢ Data volumes
¢ Hybrid ecosystems
¢ Platform criticality
¢ Enables modern business models
¢ Leverages technology and architecture
¢ 3 main integration styles (Vertical, Horizontal, Event-Driven) with respective
variations
¢ System integration and data integration are no longer disjoint disciplines
¢ Asynchronous should be the preferred communication style

Q & A

Interner Gebrauch
¢¢¢ Digitale Service Manufaktur
@OC_WIRE
OPITZCONSULTING
opitzconsulting
opitz-consulting-bcb8-1009116
WWW.OPITZ-CONSULTING.COM
Thanks for your attention!
Sven Bernhardt
Chief Architect / Integration Evangelist | Oracle ACE Director
OPITZ CONSULTING Deutschland GmbH
Kirchstrasse 6, 51647 Gummersbach, Germany
Phone: +49 172 2193529
Mail: sven.bernhardt@opitz-consulting.com
@sbernhardt
https://svenbernhardt.wordpress.com

Cloud-native Integration in the Oracle Cloud

More Related Content

What's hot (20)

Similar to Cloud-native Integration in the Oracle Cloud (20)

More from Sven Bernhardt (14)

Recently uploaded (20)

Cloud-native Integration in the Oracle Cloud