Agile development and integration with

Red Hat

Robert buljević,

Veracomp

In the beginning there was just one application, and all was

good with the world...

• But then came the 2nd app, and the 3rd

• Duplicate information (for ex. web site, CRM, ERP, department apps, web shop, etc.)

• Disconnected systems => errors, user frustration

due to manual copying, missed opportunities (omni-channel customer engagement)

• Then SaaS and cloud-based apps start appearing

• More systems => more compliance issues

• Cost escalation

• Point-to-point integrations become too complex

• Even traditional ESB integration suffers

Agile development vs integration

• Every organization has integration

problems to solve i.e. connect

business apps

• Integration is a core competency: it

surfaces customer and enterprise

data to unlock business value

• The integration function is most often a centralized bottleneck

• Therefore, “Agility” and

“Integration” are traditionally

incompatible and generate complexity&costs

The traditional ways to stitch things together...

Enterprise Integration patterns – Apache Camel

https://www.enterpriseintegrationpatterns.com/

Practical example

1. Get current flight information data from flightradar24.com2. Send email in case of emergency code

3. Find out the country on current plane position

4. Execute the following steps in parallel when plane is in Germany, Switzerland or Austria

4.1 Get weather information on plane position

4.2 Search destination airport for plane4.3 Search points of interests on plane position

5. Make aggregated information in a RSS feed available for each country

Enter web API

• REST APIs are becoming the

standard (mostly JSON format)

to expose information

•Mobile apps and single page

applications

• API-first approach

• API-as-a-business

•Modern app integration

Exposing data via web API

• Web APIs allow for integration and data

sharing

• Applications can consume the same API

• Mobile Apps

• Web apps

• Office apps (for ex. BI application, Excel,

etc)

• Read (GET) and Write (POST)

From infrastructure to app services: to speed things up,

everything is changing

Development

Process

Waterfall

CI/CD

Deployment

Server/VM

Container

Infrastructure

Data Center

Cloud

Architecture

Monolith

MicroservicesAPIs

Webservices

Service

Endpoints

Traditional vs Microservices: 2 co-existing integration

architectures

TRADITIONAL

INTEGRATION

Pattern-oriented integration

for on-premise and cloud-

based resources.

MODERN

MICROSERVICES

Create and compose

microservices using web API

and event-driven interactions.

TRANSITIONAL

INTEGRATION

Blend greenfield and

brownfield to deliver next

generation services.

Containers == the ideal way to deploy and manage

microservices

• Deploy apps as part of CI/CD pipeline,

abstracting infrastructure

• Scale automatically and on-demand

• Protect and isolate microservices

• Dynamic discovery and health checks

• Also for stateful services such as

databases and storage

• Dynamic configuration

Docker

RHEL

Docker

RHEL

Docker

RHEL

Kubernetes

Docker

RHEL

Openshift container platform: enable devops and agile

development

PRIVATE CLOUD

Deploy on-premise

PUBLIC CLOUD

Deploy on public cloud provider Deployed and managed

by Red Hat

MANAGED CLOUD

Containers: Automate from Source to Application

• Easily integrate a CVS

(github)

• Pull code from CVS and

convert it into running

application

•Now Automate this into a

CI/CD pipeline, git push to

deploy

Webhook Build Automation

•Whenever something happens in CVS, trigger some action in

Openshift

Red Hat’s Platform for Agile integration

Red Hat FUSE – distributed cloud-native

Fuse: flexible deployment

Integration pattern-based design

Integration management and container management

Red Hat FUSE Online

• Low-code platform for cloud-native

integration

• Integration Platform as a service (iPaaS)

offering based on RH Fuse

• Web-based toolchain and runtime deployed

on OpenShift

• User experience focused on solving

integration problems without writing code

• Can be deployed on Openshift on-prem as

well

Red Hat AMQ

• Standards-based messaging for the

enterprise, cloud and IoT

• Also supports event streams (based

on Apache Kafka) with durable

storage/retention

• Supports traditional message based

integration (based on ActiveMQ)

• Integrated with OpenShift, self-

service IT!

• Mutiple language support

• Database change data capture

• Easily deployed and maintained!

Red Hat API Management (3Scale)

Get your API ready for production and public consumption

•Open up your API to

the world with

confidence

• Automatically

integrate with

Openshift and Fuse

backend microservices

Integrated CMS for developers

• Self-provisioning for

developers (get API key,

authenticate, etc)

•OpenAPI docs

• Stats & analytics for my

API

Reports & Analytics

Red Hat Integration: run the latest technology anywhere,

without vendor lock-in

Start integrating now!

Red Hat as part of IBM

The world’s leading provider

of open source enterprise IT solutions

MORE THAN

90%of the

FORTUNE

500RED HAT

use

PRODUCTS &

SOLUTIONS

~13,815EMPLOYEES

105+OFFICES

40+COUNTRIES

THE FIRST

$3

OPEN

SOURCE

COMPANY

IN THE WORLD

BILLION

Product Development Model

We participate in and create

community-pow ered

upstream projects.

Participate Integrate Stabilize

We integrate upstream

projects, fostering open

community platforms.

We commercialize these

platforms together w ith a rich

ecosystem of services and

certif ications.

Upstream community projects -> Enterprise products

Red Hat Subscriptions – support, patches, expertise,

trainings, knowledge base, etc.

Thank you!