If it's for a side project, i would think about resiliency and lasting for long time once there's a need for it. This's also contributed by the stack or how you setup infra. So don't bother initially.
You can pick a framework if you're comfortable with mix of frontend and backend (rails, django etc)
If you are more on backend, pick say react in frontend and your choice of language in backend and write monolith. Have a database if needed. Avoid cache completely (You don't need to scale or make it performant). Infact you can use file based db (eg: bolt) and add Pg/Mongo/Sql later.
My usual setup is,
1. Go for backend, react frontend
2. Deployed backend in free-tier GCP VM
3. Deployed frontend in Netlify/Heroku
4. Use free pg database in Heroku
Avoid self provisioning as much as possible if you don't need the control.
If it's for Indiehacker project, would suggest to not build it right away, use nocode platform or template to setup landing page, validate and do things.
You can pick a framework if you're comfortable with mix of frontend and backend (rails, django etc)
If you are more on backend, pick say react in frontend and your choice of language in backend and write monolith. Have a database if needed. Avoid cache completely (You don't need to scale or make it performant). Infact you can use file based db (eg: bolt) and add Pg/Mongo/Sql later.
My usual setup is,
Avoid self provisioning as much as possible if you don't need the control.If it's for Indiehacker project, would suggest to not build it right away, use nocode platform or template to setup landing page, validate and do things.