SlideShare a Scribd company logo

An API-focused approach to Agile Integration

•
•
Judy Breedlove
Judy Breedlove

This document discusses an API-focused approach for agile integration. It advocates designing APIs with clients in mind, validating designs early through mocking or skeleton implementations, and favoring interoperability. The document also outlines an agile integration architecture with core, composite and application network layers and describes how containers, hybrid environments, automation, control, visibility and flexibility are important. It encourages attendees to try out the Red Hat Integration platform themselves.

1 of 21
Download to read offline
AN API-FOCUSED APPROACH FOR AGILE INTEGRATION Keith Babo Red Hat Product Management Director - Integration
THREE THINGS Avoid accidental API architectures Understand the role of integration in API-centric architectures Get “hands on” with Red Hat Integration
Strategy API-CENTRIC INTEGRATION LIFECYCLE Design Implement Deploy Manage
API STRATEGY AUDIENCE ❏ Internal API clients ❏ External API clients SCOPE ❏ Single API ❏ Multiple microservices ❏ External APIs GOVERNANCE ❏ Security ❏ Lifecycle ❏ Automation ENVIRONMENT ❏ Standalone ❏ Private Cloud ❏ Public Cloud ❏ Hybrid Cloud BUSINESS STRATEGY
AGILE INTEGRATION ARCHITECTURE 5 Core Layer External Applications Application Network Layer Containers ContainerOrchestration Composite Layer Service Interactions Cloud Native Service (Runtime 1) Enterprise Integration Patterns Cloud Native App (Runtime 2) Anti Corruption Layer Containerized App (Lift and Shift EAP) Traditional App (EAP) VMs APIManagement Policies Access Control Proxy Routing Service Composition Events Mesh DevOps Automation / Continuous Integration / Continuous Delivery (Ansible) CoreIntegration
CORE SERVICES LAYER Core Layer Containers 6 Cloud Native Service (Runtime 1) Cloud Native App (Runtime 2) Containerized App (Lift and Shift EAP) Traditional App (EAP) VMs * Brownfield and greenfield services * Microservices and monoliths * Delivered independently * Independent data contexts * Mixed connectivity
COMPOSITE LAYER Containers Composite Layer Service InteractionsEnterprise Integration Patterns Anti Corruption Layer VMs Service Composition Events Mesh * Service composition * Routing and orchestration * Data transformation * Connectivity * API ←→ Event Bridging * Legacy facade (ACL)
APPLICATION NETWORK LAYER Application Network Layer Containers 8 VMs Policies Access Control Proxy Routing * Gateway layer for services * Access and policy control * Developer onboarding * Analytics * Monetization * Scales independent of other layers
CLIENT-FOCUSED ❏ Design with the API client in mind ❏ Design with tooling fit for purpose ❏ Collaborate ASAP VALIDATE EARLY ❏ Use API mocking for early feedback ❏ Skeleton implementation can be just as good as a mock FAVOR INTEROPERABILITY ❏ Create API definitions based on standards in open communities ❏ Maximize tool portability and client generation Design Implement Deploy Manage
DEMO TIME!
HONOR THE TRUTH ❏ API Definition is the source of truth ❏ Favor generation over translation WHICH PERSONA? ❏ Developer ❏ Non-developer NOT ALL APIs ARE THE SAME ❏ Standalone ❏ Data API ❏ Orchestration ❏ Event Bridge ❏ Legacy Facade Design Implement Deploy Manage
DEMO TIME!
CONTAINERS ❏ Best way to develop services (polyglot, portability, availability, service wiring, advanced deployment, …) ❏ Maximize inner vs. outer architecture pattern HYBRID ENVIRONMENT ❏ Support integration and management of APIs living outside containerized environment ❏ Consistent architecture across private, public, and managed cloud AUTOMATE ❏ API-driven infrastructure services ❏ Ability to automate application and infrastructure services in a single pipeline Design Implement Deploy Manage
DEMO TIME!
CONTROL ❏ Securing APIs ❏ Traffic flow control via policy ❏ Policy extensibility VISIBILITY ❏ Developer onboarding and engagement ❏ Traffic and policy alerts ❏ Use analytics to understand how APIs are tracking against business objectives FLEXIBILITY ❏ Centralized management and distributed enforcement ❏ API management architecture must span multiple environments Design Implement Deploy Manage
DEMO TIME!
AGILE INTEGRATION SOLUTION STACK 17 Core Layer External Applications Application Network Layer Containers Composite Layer Service Interactions Cloud Native Service (Runtime 1) Enterprise Integration Patterns Cloud Native App (Runtime 2) Anti Corruption Layer Containerized App (Lift and Shift EAP) Traditional App (EAP) VMs Policies Access Control Proxy Routing Service Composition Events Mesh DevOps Automation / Continuous Integration / Continuous Delivery (Ansible) ContainerOrchestration APIManagement CoreIntegration ContainerOrchestration APIManagement CoreIntegration
TRY IT OUT YOURSELF!
https://www.redhat.com/en/explore/fuse-online REALLY … TRY IT OUT YOURSELF!
TODO LIST Avoid accidental API architectures Understand the role of integration in API-centric architectures Get “hands on” with Red Hat Integration
THANK YOU plus.google.com/+RedHat linkedin.com/company/red-hat youtube.com/user/RedHatVideos facebook.com/redhatinc twitter.com/RedHatNews

More Related Content

An API-focused approach to Agile Integration

  • 1. AN API-FOCUSED APPROACH FOR AGILE INTEGRATION Keith Babo Red Hat Product Management Director - Integration
  • 2. THREE THINGS Avoid accidental API architectures Understand the role of integration in API-centric architectures Get “hands on” with Red Hat Integration
  • 4. API STRATEGY AUDIENCE ❏ Internal API clients ❏ External API clients SCOPE ❏ Single API ❏ Multiple microservices ❏ External APIs GOVERNANCE ❏ Security ❏ Lifecycle ❏ Automation ENVIRONMENT ❏ Standalone ❏ Private Cloud ❏ Public Cloud ❏ Hybrid Cloud BUSINESS STRATEGY
  • 5. AGILE INTEGRATION ARCHITECTURE 5 Core Layer External Applications Application Network Layer Containers ContainerOrchestration Composite Layer Service Interactions Cloud Native Service (Runtime 1) Enterprise Integration Patterns Cloud Native App (Runtime 2) Anti Corruption Layer Containerized App (Lift and Shift EAP) Traditional App (EAP) VMs APIManagement Policies Access Control Proxy Routing Service Composition Events Mesh DevOps Automation / Continuous Integration / Continuous Delivery (Ansible) CoreIntegration
  • 6. CORE SERVICES LAYER Core Layer Containers 6 Cloud Native Service (Runtime 1) Cloud Native App (Runtime 2) Containerized App (Lift and Shift EAP) Traditional App (EAP) VMs * Brownfield and greenfield services * Microservices and monoliths * Delivered independently * Independent data contexts * Mixed connectivity
  • 7. COMPOSITE LAYER Containers Composite Layer Service InteractionsEnterprise Integration Patterns Anti Corruption Layer VMs Service Composition Events Mesh * Service composition * Routing and orchestration * Data transformation * Connectivity * API ←→ Event Bridging * Legacy facade (ACL)
  • 8. APPLICATION NETWORK LAYER Application Network Layer Containers 8 VMs Policies Access Control Proxy Routing * Gateway layer for services * Access and policy control * Developer onboarding * Analytics * Monetization * Scales independent of other layers
  • 9. CLIENT-FOCUSED ❏ Design with the API client in mind ❏ Design with tooling fit for purpose ❏ Collaborate ASAP VALIDATE EARLY ❏ Use API mocking for early feedback ❏ Skeleton implementation can be just as good as a mock FAVOR INTEROPERABILITY ❏ Create API definitions based on standards in open communities ❏ Maximize tool portability and client generation Design Implement Deploy Manage
  • 11. HONOR THE TRUTH ❏ API Definition is the source of truth ❏ Favor generation over translation WHICH PERSONA? ❏ Developer ❏ Non-developer NOT ALL APIs ARE THE SAME ❏ Standalone ❏ Data API ❏ Orchestration ❏ Event Bridge ❏ Legacy Facade Design Implement Deploy Manage
  • 13. CONTAINERS ❏ Best way to develop services (polyglot, portability, availability, service wiring, advanced deployment, …) ❏ Maximize inner vs. outer architecture pattern HYBRID ENVIRONMENT ❏ Support integration and management of APIs living outside containerized environment ❏ Consistent architecture across private, public, and managed cloud AUTOMATE ❏ API-driven infrastructure services ❏ Ability to automate application and infrastructure services in a single pipeline Design Implement Deploy Manage
  • 15. CONTROL ❏ Securing APIs ❏ Traffic flow control via policy ❏ Policy extensibility VISIBILITY ❏ Developer onboarding and engagement ❏ Traffic and policy alerts ❏ Use analytics to understand how APIs are tracking against business objectives FLEXIBILITY ❏ Centralized management and distributed enforcement ❏ API management architecture must span multiple environments Design Implement Deploy Manage
  • 17. AGILE INTEGRATION SOLUTION STACK 17 Core Layer External Applications Application Network Layer Containers Composite Layer Service Interactions Cloud Native Service (Runtime 1) Enterprise Integration Patterns Cloud Native App (Runtime 2) Anti Corruption Layer Containerized App (Lift and Shift EAP) Traditional App (EAP) VMs Policies Access Control Proxy Routing Service Composition Events Mesh DevOps Automation / Continuous Integration / Continuous Delivery (Ansible) ContainerOrchestration APIManagement CoreIntegration ContainerOrchestration APIManagement CoreIntegration
  • 18. TRY IT OUT YOURSELF!
  • 20. TODO LIST Avoid accidental API architectures Understand the role of integration in API-centric architectures Get “hands on” with Red Hat Integration