Self hosting alternatives for ecommerce site
Unanswered
Havana posted this in #help-forum
HavanaOP
Hey guys,
I'm currently building a car parts ecommerce website and I am looking for alternatives for hosting.
I will be running NextJS as the frontend and MedusaJS as the backend. The parts portfolio that we have contains thousands of parts. I have a few questions:
Would SSG or PPR be feasible for that many sites? Realistically, what would the build times be with thousands of pages? Roughly what specs would be required using an EC2 instance for example?
PPR would be a good solution but how would it be supported on self-host solutions?
What would I lose by going with the self-hosting path compared to Vercel?
Secondly, what self-hosting providers would you guys recommend?
I'm currently building a car parts ecommerce website and I am looking for alternatives for hosting.
I will be running NextJS as the frontend and MedusaJS as the backend. The parts portfolio that we have contains thousands of parts. I have a few questions:
Would SSG or PPR be feasible for that many sites? Realistically, what would the build times be with thousands of pages? Roughly what specs would be required using an EC2 instance for example?
PPR would be a good solution but how would it be supported on self-host solutions?
What would I lose by going with the self-hosting path compared to Vercel?
Secondly, what self-hosting providers would you guys recommend?
7 Replies
Saint Hubert Jura Hound
@Havana dont listen to this guy. Its an ai chatbot promiting itself.
Thousands of pages should be perfectly fine being generated statically during build. Plenty of ppl do it already.
Also ppr is no longer an experimental option and now comes enabled by default when using cache components. Which afaik they do work when self hosted but idk if its production ready. Ive seen some issues.
As for server costs and requirements, will depend mostly on user counts.
Hosting on vercel will def be more expensive but by self hosting u lose out on a good bit of DX as well as additional support and tooling. Then again youd still need a server for ur backend so might as well go fully self hosted
Thousands of pages should be perfectly fine being generated statically during build. Plenty of ppl do it already.
Also ppr is no longer an experimental option and now comes enabled by default when using cache components. Which afaik they do work when self hosted but idk if its production ready. Ive seen some issues.
As for server costs and requirements, will depend mostly on user counts.
Hosting on vercel will def be more expensive but by self hosting u lose out on a good bit of DX as well as additional support and tooling. Then again youd still need a server for ur backend so might as well go fully self hosted
As for hosting providers, depends on ur needs. Need something reliable and scalable with the option for extra infra components u could go w a cloud provider. If u just need a single VPS for a site for a few thousand users, go with OVH, hetzner (personal recommendation), DO, hostinger, doesnt rlly matter
@Saint Hubert Jura Hound <@170876868428300288> dont listen to this guy. Its an ai chatbot promiting itself.
Thousands of pages should be perfectly fine being generated statically during build. Plenty of ppl do it already.
Also ppr is no longer an experimental option and now comes enabled by default when using cache components. Which afaik they do work when self hosted but idk if its production ready. Ive seen some issues.
As for server costs and requirements, will depend mostly on user counts.
Hosting on vercel will def be more expensive but by self hosting u lose out on a good bit of DX as well as additional support and tooling. Then again youd still need a server for ur backend so might as well go fully self hosted
HavanaOP
Thank you for the real reply, I already suspected it being self promotion.
Like you say, I would still need to host my own database and backend preferably in the same instance to avoid round-back times by hosting the backend and database at a different place than the website.
Like you say, I would still need to host my own database and backend preferably in the same instance to avoid round-back times by hosting the backend and database at a different place than the website.
@Saint Hubert Jura Hound As for hosting providers, depends on ur needs. Need something reliable and scalable with the option for extra infra components u could go w a cloud provider. If u just need a single VPS for a site for a few thousand users, go with OVH, hetzner (personal recommendation), DO, hostinger, doesnt rlly matter
HavanaOP
I've been looking at flightcontrol.dev, do you have any experience with that? Looks like an easy way to manage and create AWS infrastructure
@Havana Thank you for the real reply, I already suspected it being self promotion.
Like you say, I would still need to host my own database and backend preferably in the same instance to avoid round-back times by hosting the backend and database at a different place than the website.
Saint Hubert Jura Hound
The same geographical zone at least is usually fine but if u wanna put it on the same instance that works too. Latency between servers in the same zone is usually negligible.
So if u wanna put stuff on the same instance do it bc its easier, the latency barely matters in this situation
So if u wanna put stuff on the same instance do it bc its easier, the latency barely matters in this situation
@Havana I've been looking at flightcontrol.dev, do you have any experience with that? Looks like an easy way to manage and create AWS infrastructure
Saint Hubert Jura Hound
Never heard of them but i would probably avoid the extra layer of abstraction
Ah i just looked em up and they seem to offer a lot. Id definitely carefully consider this choice bc once u make it itll be difficult to change. But if u dont wanna spend time and effort learning devops stuff it might be a good option