Speedy Component Models
summary
Claims that using per-component models plus Json API sparse field sets cuts server work, network payload and client parsing for heavy component pages — one example shows a single request touching ~200 model instances and responses bloating to ~400KB. Implementation uses Ember Data and jsonapi-resources: component model files mirror only needed attributes, an adapter builds sparse field sets recursively, and a serializer renamespaced payload to hydrate those component-scoped models.
AI-written summary · about
chapters (4)
related talks
36mComponent Model: The Final Abstraction
36mPanel: Ember at Scale
43mHundreds of components, hundreds of experiments and only one page
13mAbstract component modeling in React
26mBetter living through components
45mReact Server Components: Fad or Real Progress?
19mReact Server Components - Under the Hood
30mReact Server Components