7. Acting as shock-absorber by decoupling Domains, Systems, Teams, Development Speeds
through Usecase-driven Outside-In Design and Self-Service
The role of API’s in EA
https://github.com/Haufe-Lexware/api-style-guide/
9. Our (API) Approach @Haufe
Don’t centralize
Go for speed, not efficiency
Group APIs by
Domain
Let teams work
independently, as long as
they follow the API
Styleguide
Choose API Management
by use case, not by dogma
Apply DevOps
(Build, Test, Deploy,…)
API’s on the Domain
boundary, not domain
internal communication
11. APIops = DevOps for API Management
Container, container, container Infrastructure as Code
Inmutable Server Green-Blue Deployment
12. API Management in Production
(here Mobile SPA with Oauth 2)
ExternalLoadBalancer(Apache)
CRS
iDesk PGSQL
API Portal
Glassfish
APIm PGSQL
NFS
iDesk Redis
Kubernetes API
Jenkins,
Devs
Public
Devs
API Gateway
Mobile EAR