agile integration€¦ · 3 insert designator, if needed be competitive enterprise it is undergoing...
Post on 21-Aug-2020
6 Views
Preview:
TRANSCRIPT
AGILE INTEGRATION
Red Hat Day Toronto
Wojciech SerafinSolution ArchitectJune 20, 2018
INSERT DESIGNATOR, IF NEEDED2
● Integration – history
● Integration is getting harder. Why?
● The Agile Integration concept explained
● Red Hat Technologies to implement Agile Integration
● Agile Integration reference architecture
● Demo
● Customer success stories
AGENDA
INSERT DESIGNATOR, IF NEEDED3
BE COMPETITIVEEnterprise IT is undergoing fundamental change. To remain competitive, businesses need an integration platform capable of supporting current and next generation architectures.
Development Process
Waterfall
Deployment
Server/VM
Container
Infrastructure
Data Center
Cloud
Architecture
Monolith
MicroservicesAPIs
Webservices
Service Endpoints
DevOps
INSERT DESIGNATOR, IF NEEDED4
INSERT DESIGNATOR, IF NEEDED5
Everybody has an integration problem.
Or a problem with integration.
INTEGRATION - HISTORY
INSERT DESIGNATOR, IF NEEDED7
INTEGRATION - REVIEW
INSERT DESIGNATOR, IF NEEDED8
INTEGRATION - ESB
INSERT DESIGNATOR, IF NEEDEDINSERT DESIGNATOR, IF NEEDED9
● Stringent scalability ● Slow team co-ordination● Complex governance● Long software delivery cycle
Delay of responding to business needs
SOA AND ESB
INSERT DESIGNATOR, IF NEEDED10
Does my Bus look big in this ? – Martin Fowler and Jim Webber
“ NoESB: Don't Ride the Bus If You Don't Know Where It Goes “ - Gartner 2014
“ SOA was DOA – Why buses don’t fly in the clouds“ - Snaplogic
An ESB is not API Management - IBM
INTEGRATION IS CHANGING
INSERT DESIGNATOR, IF NEEDED12
SMACIT*
INSERT DESIGNATOR, IF NEEDED13
NEW WAVE INTEGRATION ARCHITECTURESNew 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-FOCUSEDAPIs emerging as standard interaction contact
Client-oriented vs. service-oriented
Security, scale, insight are central concerns
INSERT DESIGNATOR, IF NEEDED14
EVOLVING INTEGRATION ARCHITECTURESEmerging 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
THE RED HAT AGILE INTEGRATION CONCEPT
16
Agility“The most critical business capability today”
Src: https://www.bcgperspectives.com/content/articles/it_strategy_it_transformation_it_enabled_business_agility/
INSERT DESIGNATOR, IF NEEDED17
BRINGING AGILITY INTO INTEGRATIONMake your platform agile…not just your software
Leveraging methods and tools that allow agile and effective integration
of services, apps, APIs and data is a foundation for competitive advantage
INSERT DESIGNATOR, IF NEEDED
Build consistent Omni-channel
Experience
Enable SaaS Integrations Across
Hybrid Environments
Integrate With Cloud/Mobile/IoT
Native Apps
Build Customer Or Partner Ecosystems
Increase Internal Agility
Leverage Existing Data/Services Better
INTEGRATION: TYPICAL CHALLENGES
INSERT DESIGNATOR, IF NEEDED19
ESB
Mainframe AS/400
Centralized Hub
Hybrid Platform
API
Policies, Analytics, and Ecosystems
Loosely Coupled
Demand for More Agility
THE NEED FOR A CHANGE APPROACHES
INSERT DESIGNATOR, IF NEEDED
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
THE AGILE INTEGRATION CONCEPT BY RED HAT
INSERT DESIGNATOR, IF NEEDED21
TWO DIMENSIONS OF DISTRIBUTED INTEGRATION
DISTRIBUTEDINTEGRATION
FLEXIBILITY
WHERE INTEGRATION IS USEDIntegration at the center or the edge of your enterprise architecture.
WHO PERFORMS INTEGRATION Unlocking integration capability for new categories of integrators.
INSERT DESIGNATOR, IF NEEDED22
Agile IntegrationTraditional SB Integration
API Centric
Microservices
DevOpsCI/CD Low Code
Ad-Hoc Integration
Distributed Event Driven Data
NOT JUST A MARKETING SLOGAN
INSERT DESIGNATOR, IF NEEDED23
BE COMPETITIVE
CI/CD Container CloudMicroservicesAPIs
RED HAT TECHNOLOGIES FOR AGILE INTEGRATION
INSERT DESIGNATOR, IF NEEDED
RED HAT TECHNOLOGIES FOR AGILE INTEGRATION
DISTRIBUTEDINTEGRATION CONTAINERS APIs
Tools and processes
INSERT DESIGNATOR, IF NEEDED26
Fuse Standalone Fuse on OpenShift Fuse Online (iPaaS)
● Single JVM Fuse● Developer-focused● Integration where you
need it● “Classic” integration
● Scale out Fuse● Replaces Fabric v1● Developer-focused● “Cloud native”
integration
● Low/no-code UX● 100% cloud-based● Integration through a
browser● Fuse for the rest of us -
“Ad Hoc” integration
Based on Apache Camel, a powerful pattern-based integration engine with a comprehensive set of connectors and data formats to tackle various integration problem.
Hybrid
RED HAT FUSE
INSERT DESIGNATOR, IF NEEDED27
3SCALE – API MANAGEMENT
Access control Security
API contracts Rate limits
Analytics Reporting
Dev portal Docs
Billing Payments
Admin Console
Dev Portal
AP
I
Managem
ent
Traffic Manager
APIs
Applications
Consumers
HTTP / HTTPS
Security, usage & rate limits
INSERT DESIGNATOR, IF NEEDED28
API BASED INTEGRATION SCENARIOS
Microservices-based APIsLegacy-based APIs
Internal / External API Consumption
External API
External API
External API Consumption
Internal Integration
Integration Route
Internal API
Cloud Native Microservices
Containerized Application
Non-containerized Application
INSERT DESIGNATOR, IF NEEDED29
REFERENCE ARCHITECTURE
Core Principles:● Microservice-based architecture
(independently deployed in containers for scalability and DevOps)● Three layers of abstraction● Legacy integration● Dumb pipes -- smart endpoints● Loose-coupling via API-based integration● Stateless integration layer● Leveraging API Management on various levels
INSERT DESIGNATOR, IF NEEDED
DUMB PIPES – SMART ENDPOINTS
INSERT DESIGNATOR, IF NEEDED31
AGILE INTEGRATION ARCHITECTURE
Base Microservices Layer
- Simple Services- Application Domain Contexts
Gateway Layer
- Policies- Transformation / Routing
Composite Layer
- Service Discovery / Network Functions- Composite Microservices / EIP- Event Bus- Caching
Legacy Systems
2
1
3
DEMO
INSERT DESIGNATOR, IF NEEDED33
DEMO• A Client API
• Development on a local IDE and OpenShift
• API Management
• RedHat FUSE online
SUCCESS STORIES
INSERT DESIGNATOR, IF NEEDED35
Increase Internal Agility
Leverage Existing Data/Services Better
SaaS Integrations Across Hybrid Environments
INSERT DESIGNATOR, IF NEEDED 36
www.redhat.com/en/resources/innovation-through-agile-integration-whitepaper
THANK YOUplus.google.com/+RedHat
linkedin.com/company/red-hat
youtube.com/user/RedHatVideos
facebook.com/redhatinc
twitter.com/RedHat
INSERT DESIGNATOR, IF NEEDED
SOA
Microservices
Event-Base
Container
API
DEVOPS
START THE JOURNEY
INSERT DESIGNATOR, IF NEEDED
INSERT DESIGNATOR, IF NEEDED40
AGILE INTEGRATION
Container Container Container
Container
Clie
nt
API
Man
agem
ent
RESTFul API RESTFul APIAMQP
RESTFul API
RESTFul API
Clie
ntC
lient
API
API
API
Building lightweight smart endpoint microservice with enterprise class pattern and pre-built reusable components.
Immutable independent deployment into distributed cloud platform with secured, managed scalable and self healing capability
Composing microservice by encapsulating right granularity as a simple microservice pipeline
Intuitive, well defined, re-usable endpoint
distribute, control, and monetize APIs
Mgmt
top related