Need some advice on low bandwidth project architecture
Unanswered
West African Lion posted this in #help-forum
West African LionOP
I’ve just joined a new team as essentially the sole web developer in the team. I’m inheriting an application which to me seems to have a bit of an odd architecture. It is a relatively small site which has been split into two logical sections, one is a high bandwidth application using NextJS in SPA (static export) mode showing map data and the other is a (very) low bandwidth application using preact and preact router to allow exploring the data in a tabular format.
I’ve not used preact before but the philosophy seems to be that preact has a smaller bundled size to send down to the end users.
Whatever the case it’s made the codebase more complex than I think it needs to be!
All my gut instincts are telling me that the project makes more sense as a single NextJS application utilising server side rendering (especially for the low bandwidth where it will reduce client side querying)
Does this sound the right choice? Or does the existing setup have sound reasoning behind it?
I’ve not used preact before but the philosophy seems to be that preact has a smaller bundled size to send down to the end users.
Whatever the case it’s made the codebase more complex than I think it needs to be!
All my gut instincts are telling me that the project makes more sense as a single NextJS application utilising server side rendering (especially for the low bandwidth where it will reduce client side querying)
Does this sound the right choice? Or does the existing setup have sound reasoning behind it?
1 Reply
Scottish Fold
You can reduce the amount of requests by using server side rendering, caching the data and only revalidating the cache when data changes. https://nextjs.org/docs/app/building-your-application/caching