COTS in a Reactive Architecture
summary
A pattern to integrate a COTS e‑commerce engine into a reactive enterprise using Scala and Akka and lightweight adapters rather than rewriting the vendor monolith. Case study: a high‑scale deployment driving 10‑digit annual revenue across 25 countries that suffers cascading failures and slow delivery. The solution uses DDD and ports‑and‑adapters, iteratively building small slivers alongside the COTS, projecting read models, auditing results, and gradually switching clients — claim: faster delivery, clearer data ownership, lower vendor lock‑in, and safe progressive replacement.
AI-written summary · about
chapters (4)
related talks
27mFour Principles of Reactive Architectures
47mPorts, Adapters, and Other Ways to Stop Breaking Your Business Logic
50mA Practical Use Case of Software Architecture Evolution
01h 11mReactive Architecture Patterns Debate
45mE-commerce platform. Core build principles, problems and guidelines.
12mReactive architecture, design, and programming
34mUnleashing Agility: How Capital One Embraced COTS for NextG...
49mRethinking Reactive Architectures