Web components to me represent the architecture I’d like to have. I think a good arch could be:
1. Build a rails/django type site, make everything work vanilla http+html etc.
2. Create standalone web components for the places you need some more interactivity, like type-ahead search box, “click to add” type thing, or a datatable
So most of your performance stuff could be handled/improved on the server, focus on aggressive caching etc. and most of the complexity would be on the server with small stand-alone parts on the client (ideally without a lot of interconnection, i.e. without a big client side state manager). This would not allow full-spa but I am not convinced SPA is the answer in many/most of the cases it’s used.
1. Build a rails/django type site, make everything work vanilla http+html etc.
2. Create standalone web components for the places you need some more interactivity, like type-ahead search box, “click to add” type thing, or a datatable
So most of your performance stuff could be handled/improved on the server, focus on aggressive caching etc. and most of the complexity would be on the server with small stand-alone parts on the client (ideally without a lot of interconnection, i.e. without a big client side state manager). This would not allow full-spa but I am not convinced SPA is the answer in many/most of the cases it’s used.