Evolving from a monolithic to a distributed public API
summary
7digital shifts a single C#/WebForms codebase into a monolithic API becomes a router that delegates about 30–50 endpoints to internal-only APIs, each rebuilt or copied, enabling independent deploys, smaller codebases and easier tests. Operations use continuous delivery with Statsd New Relic Logstash monitoring, Solr for search, smarter caching and product teams per API plus pair programming. It works: fewer release bottlenecks and faster feature delivery, at the cost of implicit HTTP dependencies, inconsistent surfaces and harder global schema governance.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:43Who uses our API
- 3:28Where we came from
- 5:33Problems
- 7:54Routing
- 10:28Moving code
- 12:14API diagram
- 14:02Advantages
- 18:10How to limit chaos
- 19:46How to keep consistency
- 20:38Pair programming
- 22:00Versions
- 23:12Performance
related talks
23mOn the road from Monolith to Micro
48mTransforming a monolith to an API platform
41mEvolving your APIs, a Step by Step Approach
24mMicroservices in Practice
48mMicroMonolith
46mEvolving Your HTTP APIs: A Multi-Step Approach
27mKnow Your Developer: Changing Business for the Better
29mEnhancing Governance, Cost Efficiency, and Developer Productivity.