Manfred BortenschlagerEMEA Business Development Director for Integration Middleware

Agile Integration

Focus on Pillar 2: Containers

Red Hat Partner Webinar, May 24, 2018

Series of Agile Integration webinars for Partners

1. Intro: Agile Integration Vision

2. Agile Integration Reference Architecture

3. Focus on Pillar 1: Distributed Integration

4. Focus on Pillar 2: Containers

5. Focus on Pillar 3: APIs/API Management

https://www.redhat-partner.com/webinars_on_demand

2

3

What to expect from today...

● Recap: The Opportunity and Agile Integration Concept

● Focus on Containers

● Inner and Outer Architecture for Containers

● Red Hat OpenShift Overview

● Wrap up

The Idea behind Agile Integration

Move from product-led customer conversations …

… to customer challenge-led conversations

… which translate into solutions including various products.

What’s in it for Partners ?

Move to:

Single Product Conversations

Long-Term Customer Value Discussions

“Just” a Sales Rep for Point Solutions

Strategic Platform Partner

Becoming the strategic integration partner to your customers in a long-term relationship

Middleware: Huge Potential for Red Hat Partners

Source: Analyst and company estimates. Not to be construed as company guidance. Jan 2018.

Growth opportunity with a total addressable market estimated at ~$66B in 2020

Let’s not sell empty glasses !

Why would there be ANY deal, where we are not at least trying to sell Middleware on top of OpenShift?

Recap: The Agile Integration Concept

Why Agile Integration ?

We start from two premises:

1. “Agility” is the most important business capability today.*

2. Every organisation has integration problems to solve.

The Integration function (technically and organisationally) is most often a centralised bottleneck.This makes “Agility” impossible.

9* BCG: https://www.bcgperspectives.com/content/articles/it_strategy_it_transformation_it_enabled_business_agility/ Accenture: https://www.accenture.com/t20170328T065747__w__/no-en/_acnmedia/PDF-47/Accenture-Nordic-PDF-Agile-Fast.pdf McKinsey: https://www.mckinsey.com/business-functions/organization/our-insights/why-agility-pays

Typical Integration Challenges

Build consistent Omni-channel

Experience

Enable SaaS Integrations Across

Hybrid Environments

Integrate With Cloud Native/Mobile/IoT

Apps

Build Customer Or Partner Ecosystems

Increase Internal Agility

Leverage Existing Data/Services Better

10

For details refer to the Agile Integration Whitepaper here: << LINK >>

DISTRIBUTEDINTEGRATION

-LIGHTWEIGHT-PATTERN BASED-EVENT ORIENTED

-COMMUNITY SOURCED

FLEXIBILITY

CONTAINERS

- CLOUD NATIVE SOLUTIONS-LEAN ARTIFACTS,

INDIVIDUALLY DEPLOYABLE- CONTAINER BASED SCALING AND HIGH

AVAILABILITY

SCALABILITY

APIs

-WELL DEFINED, REUSABLE,AND WELL MANAGED

END-POINTS-ECOSYSTEM LEVERAGE

RE-USABILITY

Culture Processes Tools Automation

Business Process Management

Data Management

IoTEnablement

Enterprise Applications

Mobile Enablement

Red Hat’s Agile Integration Concept

11

12

Agile Integration Reference Architecture

Base Microservices Layer

- µs organised into application domains (based on bounded context)- Legacy integration (Think Gartner’s Bi-Modal IT)

Gateway Layer

- Separation of concerns- Access control, transformation

Composite Layer

- Composition of µs to provide business functions- Pattern-based integration, aggregations, splits, content transformation,

caching, etc.- Event-based communication, lightweight messaging

2

1

3

Capabilities

Integration Patterns

Messaging

Data Virtualization

Caching

https://www.redhat-partner.com/webinar_trainings#red-hat-agile-integration-webinar-series

Partner Webinar Recordings

Focus on Pillar 2:Containers

15

WHAT ARE CONTAINERS?It Depends Who You Ask

● Application processes on a shared kernel

● Simpler, lighter, and denser than VMs

● Portable across different environments

● Package apps with all dependencies

● Deploy to any environment in seconds

● Easily accessed and shared

INFRASTRUCTURE APPLICATIONS

16

Virtual Machines and Containers

VIRTUAL MACHINES CONTAINERS

VMs virtualize the hardware Containers isolate processes

VM

OS Dependencies

Kernel

Hypervisor

Hardware

App App App App

Hardware

Container Host (Kernel)

Container

App

OS deps

Container

App

OS deps

Container

App

OS deps

Container

App

OS deps

17

Containers: Separation of Concerns

Container Host

Container

Application

OS dependencies

Dev

IT OpsInfrastructure

Virtual Machine

Application

OS dependencies

Operating System

IT Ops(and Dev, sort of)

Infrastructure

Clear ownership boundary between Dev and IT Ops

Drives DevOps adoption and fosters agility

Optimized for stability

Optimized for agility

18

APPLICATION PORTABILITY WITH CONTAINERS

Container

Application

OS dependencies

Container

Application

OS dependencies

Container

Application

OS dependencies

Container

Application

OS dependencies

Container

Application

OS dependencies

LAPTOP

Guest VM

RHEL

BARE METAL

RHEL

VIRTUALIZATION

Virtual Machine

RHEL

PRIVATE CLOUD

Virtual Machine

RHEL

PUBLIC CLOUD

Virtual Machine

RHEL

RHEL Containers + RHEL Host = Guaranteed PortabilityAcross Any Infrastructure

Containers: Inner and Outer Architecture

The Inner and Outer Architecture of Container Platforms

Concept by Gartner’s Gary Olliffe

Src: https://blogs.gartner.com/gary-olliffe/2015/01/30/microservices-guts-on-the-outside/

20

Src

: Gar

y O

lliffe

.ht

tp://

blog

s.ga

rtner

.com

/gar

y-ol

liffe

/201

5/01

/30/

mic

rose

rvic

es-g

uts-

on-th

e-ou

tsid

e/

Src

: Gar

y O

lliffe

.ht

tp://

blog

s.ga

rtner

.com

/gar

y-ol

liffe

/201

5/01

/30/

mic

rose

rvic

es-g

uts-

on-th

e-ou

tsid

e/

Src

: Gar

y O

lliffe

.ht

tp://

blog

s.ga

rtner

.com

/gar

y-ol

liffe

/201

5/01

/30/

mic

rose

rvic

es-g

uts-

on-th

e-ou

tsid

e/

24

Key Aspects of the Outer Architecture

The Outer Architecture delivers the platform capabilities you need to help all those simple little microservices (and their DevOps teams) work together to make good on the promises of flexible and scalable development and deployment.

It is coping with this complexity that makes [the software development lifecycle] discipline and automation an essential element of delivering microservice architecture.

Src: https://blogs.gartner.com/gary-olliffe/2015/01/30/microservices-guts-on-the-outside/

“

Agile Integration Pillar 2: Containers

with Red Hat OpenShift

26

Red Hat OpenShift Container PlatformTransform development and operations

Deploy & manage containers/apps

Seamless across hybrid clouds

Automated and scalable

Shift to a containerized, DevOps deployment model

Consistency across environments

Key microservices enabler

Community Powered Innovation

10,000 foot overview

OpenShift runs on your choice of infrastructure

Nodes are instances of RHEL where apps will run

Apps and components run in containers

Container Image

Container

Pod

Masters are the Control Layer

The Master’s jobs

Service Layer for application discovery and communication

What about app data?

Routing layer for external accessibility

Access via Web UI, CLI, IDE, API

Outlook: What’s to come on OpenShift wrt Integration

Red Hat AMQ StreamsHigh-throughput, low-latency framework for real-time data feeds and streaming apps.

Implemented as an distributed transaction log to achieve an extremely scalable pub/sub message queue.

Outlook: What’s to come on OpenShift wrt Integration

https://developers.redhat.com/blog/2018/05/07/announcing-amq-streams-apache-kafka-on-openshift/

Agile Integration: Containers

Sales Perspective

Typical Buying Personas

STRATEGIC ARCHITECTURAL BUSINESS

What constraints are your current integration systems placing on your business in

the next 18 months?

What is your current strategy around

microservices? Or APIs?

How fast are you able to evolve your customer facing

systems? What tend to be the blockers in terms of

getting new systems live?

Persona: CIO Persona: Chief architect Persona: Product leader

Answers that point to Agile Integration

STRATEGIC

● Faster to market● Agility & flexibility ● Re-use● Cost savings● Maintainability● Scalability● M&A

ARCHITECTURAL

● Microservices ● API-first● Migrating from

existing ESBs ● Adopt next-gen

architecture● Percentage cloud ● Hybrid cloud

BUSINESS● Partner programs● SaaS integration● Foundations for Mobile ● Citizen Integrator

support● Multichannel delivery● Analytics & intelligence● Becoming a “platform”

ALL CONNECTED

Container-led Scenarios

Containers

APIsIntegration

Scalability

Microservices

“Platform”

Cost savings

Maintainability

Hybrid cloud

Strategic:

Architectural:

Business:

Let’s not sell empty glasses !

Add value with Middleware on top of OpenShift

Wrap-up

Take-awaysThe Agile Integration concept should help to move to customer challenge-led and solution-oriented conversations.

Three pillars make up the Red Hat Agile Integration concept. There is no vendor lock-in.

The 2nd pillar suggests Containers as an architectural concept.

An effective container platform must cover the inner and outer architecture.

OpenShift is Red Hat’s container platform product.

OpenShift allows a range of different deployment options to implement hybrid-cloud scenarios.

47

More about Agile Integration: Whitepaper

48

www.redhat.com/en/resources/innovation-through-agile-integration-whitepaper

49

“The Role of Agile Integration in Open Banking”

https://internationalbanker.com/banking/agile-integration-open-banking/

● Red Hat Webinar series for Partners https://www.redhat-partner.com/webinar_trainings#red-hat-agile-integration-webinar-series

● Agile Integration Classroom Workshop https://www.redhat-partner.com/trainings#agile-integration-workshop

● Agile Integration Sales Day https://www.redhat-partner.com/trainings#sales-day-agile-integration

Partner Enablement Activities

Manfred BortenschlagerEMEA Business Development Director for Integration Middleware

Agile Integration

Focus on Pillar 2: Containers

Red Hat Partner Webinar, May 24, 2018

-- The End --

52

Virtual Machine

Application

OS dependencies

Operating System

VIRTUAL MACHINES AND CONTAINERS

VM IsolationComplete OSStatic ComputeStatic MemoryHigh Resource Usage

Container IsolationShared KernelBurstable ComputeBurstable MemoryLow Resource Usage

Container Host

Container

Application

OS dependencies

53

Virtual machines are NOT portable across hypervisor and do NOT provide portable packaging for applications

APPLICATION PORTABILITY WITH VM

VM Type X

Application

OS dependencies

Operating System

BARE METAL PRIVATE CLOUD PUBLIC CLOUDVIRTUALIZATIONLAPTOP

Application

OS dependencies

Operating System

VM Type Y

Application

OS dependencies

Operating System

VM Type Z

Application

OS dependencies

Operating System

Guest VM

Application

OS dependencies

Operating System

What about unhealthy Pods?

The Master remediates Pod failures

Pods are the orchestrated unit in OpenShift

API and Authentication

Desired and Current State

Scheduler Pulls From The Registry

Orchestration and Scheduling

61

ANYCONTAINER

Amazon Web Services Microsoft Azure Google CloudOpenStackDatacenterLaptop

ANYINFRASTRUCTURE

APPLICATION LIFECYCLE MANAGEMENT

ENTERPRISE CONTAINER HOST

CONTAINER ORCHESTRATION AND MANAGEMENT(KUBERNETES)

OPENSHIFT CONTAINER PLATFORM

Services connect application components