Microservices in the Rhythm of ABBA
summary
A new retail credit process called ABBA is implemented as OpenShift-hosted Docker microservices with Java 11 backends and Angular frontends (upgrading 12→13), using Git/Jenkins/Maven for CI/CD and Kibana for observability. Camunda was adopted to orchestrate many human and automated tasks (replacing a previous Activity-based solution) after workshops and training, and one integration (NBP exchange rates) had to be rebuilt due to mismatched business-data sources. The project is about one third complete, and the main recurring problem is people and coordination across seven teams rather than the technology.
AI-written summary · about
chapters (11)
- 0:00ABBA and microservices intro
- 3:56ABBA platform tech stack
- 7:29Human role in sync
- 10:44People weakest link
- 14:19Development errors and experiments
- 18:30Bank org approach change
- 24:30Microservice architecture challenges
- 27:19IT infrastructure and security
- 34:20Frontends and microfrontends
- 37:50Technology choice humility
- 40:01Q&A
related talks
51mCompetitive retail architecture with microservices
38mFrom Monolith to Microservices at Zalando
31mSharing is caring: Building a modern microservice architecture helps everyone get ahead
44mRoute to microservices the epic voyage of a fintech leader
27mSlicing 'Big Elephant' systems into micro-services
01h 07mTheory and Practice of the Big Bang
18mMicroservices Out In the Wild
30mMonolith to Microservices