Web applications: splitting the monolith
summary
Demonstrates how modern web apps accumulate huge dependency bloat with concrete measurements (e.g., a 3-line replacement for a 2,100-line library, packages with ~310 recursive deps, builds growing from 512 KB to 27 MB, and a 20 MB hello-world bundle). Names the ecosystem tools involved—npm, Travis, TAP, LevelDB, Node streams, React/Redux and bundlers—and proposes research directions: splitting bundles by route/component, treating functions as data stored and synced from a database, and fetching the dependency graph incrementally rather than shipping everything.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 9:32Library dependency issues
- 15:38Inefficient package examples
- 22:03Web tech evolution
- 29:22Data and function model
- 34:16Q&A
related talks
45mA Software Architect's Approach towards SPA Based Micro Apps
24mScaling Frontend Development using Micro-frontends
16mHow to prepare a distributed nodejs application
24mMicrofrontends
57mHow I sliced your app
12mLiberating your Application from Framework Tyranny
01mHow npm split a monolith and lived to tell the tale
46mMicro Frontends, Keep Using That Word, I Don’t Think It Means What You Think It Means