Mind the gap: closing the rift between front and back
summary
Presents a front-end scaling approach that splits the app into independently owned modules wired together by deep-link contracts, supported by shared module bases and a local demo app for integration. Uses per-module CI with nightly master builds, staged/beta rollouts, custom feature flags and microsites for rapid experiments; reported outcomes include 2.5× higher release frequency, 4× faster time-to-production, ~10× fewer bugs per release, and the ability to double the front-end team without new bottlenecks.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:57Continuous Delivery Experimentation
- 6:56Efficient Memory Usage
- 15:54Core Business Code Tested. Validation of the Default App Version. The Whole Team is Responsible for Testing Features.
- 16:23Team Metrics to Measure Quality. Quarterly Continuous Quality Improvement Goals. Business Health Measurement.
related talks
27mMicro Frontends: Break Up You Web App!
24mScaling Frontend Development using Micro-frontends
37mDemystifying Micro-Frontends
22mRoad to Module Federation
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
14mMicro-frontends: Is it a Silver Bullet?
41mMicro-frontends: the golden circle