4 ms·
I imagine this will lead to many more nodejs servers.. and in turn many more CPU/s spent per user than mostly static cachable resources. Will it have a big
by londons_explore 6y ago
I imagine this will lead to many more nodejs servers.. and in turn many more CPU/s spent per user than mostly static cachable resources.
Will it have a big impact on aws usage?
- danabramov 6y agoWe have some ideas about how static caching integrates into this (for component subtrees). But this is definitely much further ahead into the future. You're right there is a tradeoff here. However, that's also part of the point. When the tradeoff isn't right, you can move much of your logic back to the client -- the point is the fluidity and the ability to choose.