agile integration an api-focused approach for · three things avoid accidental api architectures...

21
AN API-FOCUSED APPROACH FOR AGILE INTEGRATION

Upload: others

Post on 08-Oct-2020

12 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

AN API-FOCUSED APPROACH FOR AGILE INTEGRATION

Page 2: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

THREE THINGS

Avoid accidental API architectures

Understand the role of integration in API-centric architectures

Get “hands on” with Red Hat Integration

Page 3: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

Strategy

API-CENTRIC INTEGRATION LIFECYCLE

Design Implement Deploy Manage

Page 4: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

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

Page 5: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL AGILE INTEGRATION ARCHITECTURE

Page 6: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

CORE SERVICES

* Brownfield and greenfield services

* Microservices and monoliths

* Delivered independently

* Independent data contexts

* Mixed connectivity

Page 7: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

COMPOSITE

* Service composition

* Routing and orchestration

* Data transformation

* Connectivity

* API ←→ Event Bridging

* Legacy facade (ACL)

Page 8: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

CONTROL and DISPATCH

* Gateway layer for services

* Access and policy control

* Developer onboarding

* Analytics

* Monetization

* Scales independent of other layers

Page 9: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL API CENTRICDEVELOPMENT

Bounded Context

Bounded Context

External Gateway

CONTRACT-FIRST

CODE FIRSTBrown Field

Page 10: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

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

FAVORINTEROPERABILITY

❏ Create API definitions based on standards in open communities

❏ Maximize tool portability and client generation

Design Implement Deploy Manage

Page 11: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

DEMO TIME!

Page 12: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

Design Implement Deploy Manage

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

Page 13: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

DEMO TIME!

Page 14: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

Design Implement Deploy Manage

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

Page 15: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

DEMO TIME!

Page 16: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

Design Implement Deploy Manage

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

Page 17: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

DEMO TIME!

Page 18: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

AGILE INTEGRATION SOLUTION STACK

18

Page 19: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

Dev ToolsDocs

Test Tools

Page 20: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL

TODO LIST

Avoid accidental API architectures

Understand the role of integration in API-centric architectures

Get “hands on” with Red Hat Integration

Page 21: AGILE INTEGRATION AN API-FOCUSED APPROACH FOR · THREE THINGS Avoid accidental API architectures ... Design with the API client in mind Design with tooling fit for purpose ... API

CONFIDENTIAL