The document discusses iPaaS 2.0, focusing on Fuse Integration Services built for integration with OpenShift, leveraging Docker and Kubernetes for microservice deployments. It outlines the capabilities of the microservices platform, including integrated tools for application logging, metrics, tracing, and API management. The platform emphasizes continuous integration and deployment through Jenkins pipelines and supports various programming languages for flexible microservices development.

2. iPaaS 2.0: Fuse Integration Services
Keith Babo and Rob Davies

3. Integration Platform as a Service
iPaaS
Cloud-Based
Cloud
Connectivity
Citizen
UX
API
Management
Cloud
Toolchain
Data
Integration
Application
Integration
Delivery
Lifecycle
Multi-Platform

4. Two Faces of iPaaS
or ...

5. So What?
Build Deliver Scale

6. Fuse Integration Services for OpenShift
Native integration with Docker, Kubernetes, and OpenShift
Built-for-purpose application runtime ideal for microservice deployments
DevOps friendly deployment workflows
Deep inspection into integration services with domain-specific administration views
Containerized integration services
FIS 1.0 Released in Dec 2015
OpenShift Enterprise
OpenShift Dedicated

7. Fuse Integration Services for OpenShift
Integrate, cluster, and scale
applications using Kubernetes.
Tooling creates a complete runtime
customized to an application’s
requirements and delivered as a
Docker image
Bridge development and
operations with build,
deployment, and management
integration within OpenShift.

8. Microservices Platform – the Foundations
• Runtime Registry
• Logging
• Security
• Deployment
• Scalability
• Loosely coupled
• Resilient
• Temporal
From the platform: The services:

9. Kubernetes: Container Orchestration
• Automatic bin packing
• Self healing
• Horizontal Scaling
• Service Discovery and load balancing
• Automated rollouts and rollbacks
• Secret and Configuration management
• Storage orchestration
• 2 years old – 30,000 commits

11. iPaaS 2.0 Microservices Platform
• Built on top of OpenShift
• Provides additional services to generate, build and test integration
services
• Integration Services use Apache Camel:
–deployed in Spring Boot
–In a Docker Container

12. iPaaS 2.0: Microservices Platform
Citizen
Developer
iPaaS Console
Expert Developer
Can view what’s
under the hood
Administrator
Can look at Pod
donuts …
OpenShift Dedicated
Component
Catalog
Integration
Editor
Funktion
Editor
Data
Mapper
Artifact
Repository
Git
Repository
Application
Logging
Application
Metrics
Tracing
Project
Wizards
Code
Quality
Automated
Testing
Circuit
Breaker
ChatOps

13. Microservices Platform – Application Logging
• Essential part of
understanding and
diagnosing distributed
Microservices
• Uses ElasticSearch for
storage
• Fluentd for collection
• Kibana for front end

14. Microservices Platform – Application Metrics
• Historical metrics
required for
diagnosis,trends, and
auto scaling
• Uses Prometheus for
storage
• Grafana for front end

15. Microservices Platform – Tracing: Zipkin
• Zipkin: distributed tracing
framework:
• Manages both the
tracing and lookup of the
data.
• All routes for iPaaS use
camel-zipkin to record
incoming and outgoing
Camel messages
• OpenTracing

16. Microservices Platform – Tracing: Zipkin
Architecture

17. API Management:
Applying governance policies to API
requests at runtime.

18. Continuous Improvement

19. Agility: Integrated CI/CD
• Continuous
Deployment
automatically, with
jenkins pipelines for
your integration
services
• Automated tests
• Hooks for manual
approval before
production

20. Funktion
• Event driven lambda style Microservices, built on top of Kubernetes
• Polygot - supports Java, Node.js, Groovy, Kotlin, Go …
• Supports hundreds of trigger endpoint URLs
• Trigger endpoint defined in funktion.yml:
rules:
- trigger: http://0.0.0.0:8080
action: io.fabric8.funktion.sample.Main

21. But … the user just sees this:

22. POWER UP and PARTY DOWN
with Red Hat Mobile, Middleware
and OpenShift.
Wednesday evening 9PM – 12AM
Pick up your invitation for the party that
beats all parties at:
Mobile, Middleware or OpenShift
demo pods in the Red Hat Booth,
Partner Pavilion

23. Questions?

24. Highlight Content Slides are Blue

25. Section Header Slides are Yellow