Presentation at Red Hat's "Microservices, API, Containers, & Integration" day, Tustin, CA, June 21, 2018.

1. Yossi Koren
Sr. Solution Architect, Application Platform Tiger Team SAs
June 2018
API Integration: Red Hat Perspective

2. AGENDA
The Changing World of Integration
New Architectural Approach - Agile Integration
Red Hat Integration Technology Portfolio
Applying Agile Integration

3. API Driven Integration is Changing the World!
Transportation E-commerce Travel
Communication Finance & Banking

4. THE WAY WE DO BUSINESS HAS CHANGED
THE NUMBERS TELL THE STORY (AND IT’S NOT OVER YET)
90%
of all data was
created in the
last 2 years [1]
BIG DATA
77%
of Americans
own a
smartphone
[2]
MOBILE
85%
of customers
making a major
purchase start
online [3]
SOCIAL
41%
of enterprise
workloads are
running on
cloud [4]
CLOUD
29B
devices
connected to
the internet
by 2022 [5]
IoT
$284B
in mobile
commerce in
the US by
2020. [6]
API ECONOMY
[1] IBM, 10 Key Marketing Trends for 2017, Dec 2016. [2] Pew Research Center, Mobile Fact Sheet, Jan 2017. [3] Synchrony Financial, 2016 Major Purchase Study, Dec 2016.
[4] 451 Research, Voice of the Enterprise: Cloud Transformation, September 2016. [5] Ericcson, Ericcson Mobility Report, Nov 2016.
[6] Business Insider, The Rise of M-Commerce: Mobile Shopping Stats & Trends, Dec 2016.

5. Development Process
Waterfall
CI/CD
Deployment
Server/VM
Container
Infrastructure
Data Center
Cloud
Architecture
Monolith
MicroservicesAPIs
Webservices
Service Endpoints
AGILE TEAMS CANNOT GET INTEGRATION FROM
LAST GENERATION PRODUCTS
Enterprise IT is undergoing fundamental change. To remain competitive, businesses need
an integration platform capable of supporting current and next generation architectures.

6. “APIs are most valuable for
creating new business models
while removing barriers by
integrating platforms and apps
so organizations can quickly
launch new products and
services and scale faster”.
Forbes, 2017
Source: https://www.forbes.com/sites/louiscolumbus/2017/01/29/2017-is-quickly-becoming-the-year-of-the-api-economy/#5d2c6fb86a41

7. INTEGRATION IS CRITICAL FOR MODERN BUSINESS
"Only a small percentage of companies will
gain competitive advantage from SMACIT
[social, mobile, analytics, cloud, and Internet
of things] technologies. Those that do will
focus less on the individual technologies and
more on how they rally all those technologies,
in unison, to fulfill a distinctive purpose."
HARVARD BUSINESS REVIEW
Jan 2015
Source: Jeanne W. Ross, Cynthia M. Beath, & Ina Sebastian for HBR, https://hbr.org/2015/01/why-nordstroms-digital-strategy-works-and-yours-probably-doesnt Jan 2015.
Hybrid Platform
API
Policies, Analytics,
and Ecosystems
Agile Integration

8. COMMON CHALLENGES IN
MODERN APPLICATION DEVELOPMENT
Data Access for
Business Users
Building Scalable Infrastructure
Customer &
Partner Access
Enable Customer
Facing Apps via
Many Channels
IoT Devices &
Architectures
Extend Legacy
Applications
Integrate SaaS
Apps

9. “We’re losing time and
money with systems, apps,
and technologies that don't
talk to each other. How do
we integrate all parts of our
business to work
together?”

10. Source: Jeanne W. Ross, Cynthia M. Beath, & Ina Sebastian for HBR, https://hbr.org/2015/01/why-nordstroms-digital-strategy-works-and-yours-probably-doesnt Jan 2015.
TOP INTEGRATION NEEDS
SPEED, SIMPLICITY, & COLLABORATION EVERYWHERE (FROM ANYWHERE)
EASY-TO-USE
TOOLS & PROCESSES
Internal AND external
integration includes
partners & customers.
Agile development
requires a fast turn-
around. Create &
connect new apps
quickly.
Integration across the
organization means
getting non-technical
users involved.
SPEEDY
SERVICE
INCREASED
COLLABORATION

11. CLASSIC INTEGRATION ARCHITECTURES
Tried and trued approaches to integration used over the last 20+ years
POINT-TO-POINT (P2P)
Tactical, “get it done” solution
Bespoke implementation
Tightly coupled architecture
STAR/BUS TOPOLOGY
Specialized EAI and ESB architecture
Centralize integration functions
Reusable services, connectivity
BUSINESS-TO-BUSINESS (B2B)
P2P across company boundaries
Batch/document-oriented
Tight data coupling
Human-intensive, brittle process

12. NEW WAVE INTEGRATION ARCHITECTURES
New approaches to integration for next generation applications.
BROWNFIELD SHADOW
New services developed in greenfield
Data and systems live in brownfield
Delegate/facade services required
DIY INTEGRATION
Data/events from multiple sources
Integration code > business logic
Danger of entangled monolith
MICROSERVICES
Disparate data models require
transformation
Composition and conditional routing
Loose coupling a must
API-FOCUSED
APIs emerging as standard interaction
contact
Client-oriented vs. service-oriented
Security, scale, insight are central
concerns

13. EVOLVING INTEGRATION ARCHITECTURES
Emerging adoption of these approaches as market evolves and business demands dictate change.
AUTOMATION
Rate and complexity of change ++
Apps aren’t waiting for integration
Continuous delivery a must for agility
SELF-SERVICECLOUD-NATIVE
LOB stakeholders love SaaS
Low-code UX to enable non-developers
No installation, management of infra
Packaged, optimized for containers
Native integration with orchestration
and deployment
Portable across clouds

14. Red Hat Integration Portfolio

15. API INTEGRATION FRAMEWORK
API Strategy
API Development &
Integration
API Management
API Operations
New API
Development
Legacy SystemsGateway
Dev
Portal
Analytics
Automation Dev Ops Continuous Integration and Delivery
Rate Limiting
Security
Authentication
MicroservicesComposite APIs

16. THREE PILLARS FOR AGILE INTEGRATION
Key capabilities for modern software application agility
DISTRIBUTED
INTEGRATION
❏ Lightweight
❏ Pattern Based
❏ Event Oriented
❏ Community Sourced
MICROSERVICES
CONTAINERS
❏ Cloud Native Solutions
❏ Lean Artifacts
❏ Individually Deployable
❏ Container Based Scaling
and High Availability
APIs
❏ Well Defined
❏ Reusable
❏ Well Managed
End-points
❏ Ecosystem Leverage
FLEXIBILITY SCALABILITY RE-USABILITY

17. THREE PILLARS FOR AGILE INTEGRATION
Key capabilities for modern software application agility
DISTRIBUTED
INTEGRATION
-LIGHTWEIGHT
-PATTERN BASED
-EVENT ORIENTED
-COMMUNITY
SOURCED
CONTAINERS
- CLOUD-NATIVE
SOLUTIONS
-LEAN ARTIFACTS,
INDIVIDUALLY
DEPLOYABLE
- CONTAINER-BASED
SCALING AND HIGH
AVAILABILITY
APIs
-WELL-DEFINED,
REUSABLE,
AND WELL-MANAGED
ENDPOINTS
-ROBUST ECOSYSTEM
Culture, tools, processes, & automation
Mobile enablement IoT enablement
Business process
management
Decision services
(Business Rules)

18. Deploying your API Integration

19. Source: Jeanne W. Ross, Cynthia M. Beath, & Ina Sebastian for HBR, https://hbr.org/2015/01/why-nordstroms-digital-strategy-works-and-yours-probably-doesnt Jan 2015.
TOP INTEGRATION NEEDS
SPEED, SIMPLICITY, & COLLABORATION EVERYWHERE (FROM ANYWHERE)
Open and decoupled
architecture
Enterprises are moving
away from lock-in all-
or-nothing solutions to
take advantage of new
agile approach.
Enterprises are looking for
emerging, high-traffic,
critical-workload solutions
with No single points of
failure. Built for
automation from the
ground up.
Enterprises are
leveraging new
architecture models to
effectively apply cross-
functional policies
Scalable and cost
effective
No vendor lock-in,
adjacent capabilities
Multiple deployment
options to support the new
Infrastructure Paradigm:
Reliable, Rapidly
Deployable, Efficient
Infrastructure ANYTIME,
ANYWHERE.
Flexible and reliable
deployment model

20. API-CENTRIC INTEGRATION FRAMEWORK
RBDMS
SAP
NoSQL
WS
REST
JMS
+ more
FUSE INTEGRATION
SERVICE
Red Hat Fuse
Service API
Red Hat Fuse
Service API
Red Hat Fuse
Service API
Developers
Partners
Mobile App
Affiliates
Internal Projects
+ more
API MANAGEMENT
Access control and
security
API contracts and
rate limits
Analytics and
reporting
Developer portal
and docs
Billing and payments
Integration
Layer
API Service
Layer
API Service
Catalog

21. API Integration Platform

22. Fuse Standalone Fuse on OpenShift Fuse Online (iPaaS)
● Single JVM Fuse
● Developer-focused
● Integration where you need it
● “Classic” integration
THE NEXT GENERATION OF RED HAT FUSE
Three Product Distributions for Fuse 7
● Scale out Fuse
● Replaces Fabric v1
● Developer-focused
● “Cloud native” integration
● Low/no-code UX
● 100% cloud-based
● Integration through a browser
● “Ad Hoc” Integration

23. CORE FUSE
FUSE STANDALONE
OS
JVM
EAP Spring Boot Karaf
Narayana Undertow A-MQ CXF
Camel
DevStudio
Hawtio

24. SPRING BOOT
FUSE CONTAINER BASE IMAGES
Spring Boot
Application-Specific Fuse Dependencies
Application Code and Configuration
fuse-java-openshiftfuse-karaf-openshift
KARAF
fuse-eap-openshift
EAP
Apache Karaf
Application-Specific Fuse Dependencies
Application Code and Configuration
EAP Base Image
Camel Wildfly Subsystem
Application Code and Configuration
OpenJDK 8
RHEL 7

25. Self-service Integration
Low code integration platform for everyone
Fuse Online
Integration
Connectors
Customizations
Self-service
Drag and drop integrations
Runtime debug and activity
trace
Built-in connectors
- AMQ
- Database
- Salesforce and
more...
Customize Connectors
- Highly customizable
connectors from
developers
API Client Service Setup
from Swagger Documents
Customize Connectors,
code, component injections

26. RED HAT FUSE ONLINE
LOW-CODE PLATFORM FOR CLOUD-NATIVE INTEGRATION, HOSTED ON OPENSHIFT ONLINE

27. API Management Platform

28. SaaS
Hosted API manager on
3scale scalable AWS platform
with built-in redundancy,
High-availability and SLA
Openshift
Openshift API manager - API
Management Platform (AMP) 2.x,
provides an OpenShift template
to deploy AMP onto OpenShift
Container Platform (OCP)
API Manager - Policy Management
Deployment Options

29. API Gateway - Policy Enforcement
Deployment Options
OpenShift (OCP)Native
API Gateway
Application
OpenResty (NGINX +
LUA) for Red Hat
Enterprise Linux
Container
API Gateway
Application
Docker-formatted
container image from
Red Hat Registry
API Gateway
Application
OpenShift Template
Inside or Outside the
same API Manager
Cluster
API Integration
(Plug-in)
Service Management
API Client Gateway
API can be called
directly from
anywhere for greater
flexibility

30. Deployment Options
On-premise: Self-managed APIs & External Self-managed Gateway
Real Time Admin Portal
Sync / Authorize
API
Backend
API Gateway
(Native/Docker)
API Manager
API Provider
Administrators
Mobile Apps Developer Apps
Branded Dev PortalSwagger Doc
API Consumers
Developers
RH-SSO

31. Take Aways...

32. THANK YOU FOR YOUR TIME!
● APIs will very likely be a key architectural
component for most organizations
● Red Hat is investing heavily and aiming to be a
long term partner
● Agile Integration, Container Management, and API
Management will be a key architectural pillars for
the next 3-5 years

33. FOLLOW UP MATERIAL
● Red Hat Integration homepage: https://www.redhat.com/en/technologies/jboss-
middleware/integrate
● “Inside mind of a successful platform architect / Gartner APPS 2016”
https://www.slideshare.net/3scale/inside-mind-of-a-successful-platform-architect-
gartner-apps-2016
● “API Model Canvas for successful API strategies and programs”
https://www.slideshare.net/3scale/api-model-canvas-for-successful-api-strategies-and-
programs
● “The API Owner’s Manual” https://www.redhat.com/en/resources/3scale-api-owners-
manual-ebook

34. THANK YOU
plus.google.com/+RedHat
linkedin.com/company/red-hat
youtube.com/user/RedHatVideos
facebook.com/redhatinc
twitter.com/RedHat