API Strategy @ Haufe-Lexware
Daimler OneAPI Forum 2017
whoami
Stuff I have worked on
Microservice Architecture @ Haufe
Microservice Architecture is informed by
http://martinfowler.com/articles/microservices.html
Architecture is hard to change
Microservice architecture makes change easier
It is an ecosystem architecture
It is doing like the ‘web’
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/
Doing it like the ‘web’ ?
VS.
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
Doing it like the ‘web’ !
APIops = DevOps for API Management
Container, container, container Infrastructure as Code
Inmutable Server Green-Blue Deployment
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
Books to Read
Innovation happens by connecting people,
NOT computer
Stay in Touch
http://dev.haufe-lexware.com/state-of-our-api-strategy/
http://dev.haufe-lexware.com/introducing-wicked-haufe-io/
http://dev.haufe-lexware.com/ | @HaufeDev
https://www.linkedin.com/in/hrreinhardt/ | @hlgr360
Read more about our journey
Haufe API Strategy

Haufe API Strategy