I have no experience with ecommerce systems, so I wouldn't place much weight on my advice.
Between next.js and gatsy, I would choose next.js because it can support incremental server side generation of content, which means your rebuild times can be fast, while allowing your full catalog of product pages to be generated as they are accessed. Remix's server side rendering might be interesting as well.
In an ideal world, python / ruby / golang server side rendering would smoothly interoperate with client side hydration in frameworks that already existed, instead of just having node + js for that option. Then I would pick python server side rendering combined with js client side hydration.
Update: golang has "bud" framework for ssr with js views. So, just waiting for ruby and python ssr frameworks.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have no experience with ecommerce systems, so I wouldn't place much weight on my advice.
Between next.js and gatsy, I would choose next.js because it can support incremental server side generation of content, which means your rebuild times can be fast, while allowing your full catalog of product pages to be generated as they are accessed. Remix's server side rendering might be interesting as well.
True, they all have their pros and cons
In an ideal world, python / ruby / golang server side rendering would smoothly interoperate with client side hydration in frameworks that already existed, instead of just having node + js for that option. Then I would pick python server side rendering combined with js client side hydration.
Update: golang has "bud" framework for ssr with js views. So, just waiting for ruby and python ssr frameworks.