There is what modern JS world calls 'SSR' (server-side rendering) which is where, yes, you basically have a node server running to generate the HTML that is sent to the browser and that's then 'hydrated' into a client-side app. Doesn't necessarily have to be Node/JS though, other languages have their own frameworks, but JS is probably most common. This setup can then be fronted by a CDN for caching purposes.
That's not really related to the bucket concept though, it just runs on a normal server and serves everything (static and dynamic content), typically.
IMO the benefits of SSR (vs SSG or a pure static-file site) are marginal _unless_ you have a very specific use case. E.g. an ecommerce site where you want all your product pages to have great SEO, but you've got too many products to build them all at once.
Then again if you _only_ need a website (i.e. no API for other clients) then it can be nice to have end-to-end types in that kind of fullstack setup.
> Does integrating a payment processor like Shopify require something more than static hosting?
I don't know about Shopify but for e.g. Stripe you can do a lot on their hosted pages, without your own backend. If you want to automate things though, have user state based on payments, etc you will need a backend and a data store of some kind. But that could be an API that your static site points to.
There is what modern JS world calls 'SSR' (server-side rendering) which is where, yes, you basically have a node server running to generate the HTML that is sent to the browser and that's then 'hydrated' into a client-side app. Doesn't necessarily have to be Node/JS though, other languages have their own frameworks, but JS is probably most common. This setup can then be fronted by a CDN for caching purposes.
That's not really related to the bucket concept though, it just runs on a normal server and serves everything (static and dynamic content), typically.
IMO the benefits of SSR (vs SSG or a pure static-file site) are marginal _unless_ you have a very specific use case. E.g. an ecommerce site where you want all your product pages to have great SEO, but you've got too many products to build them all at once.
Then again if you _only_ need a website (i.e. no API for other clients) then it can be nice to have end-to-end types in that kind of fullstack setup.
> Does integrating a payment processor like Shopify require something more than static hosting?
I don't know about Shopify but for e.g. Stripe you can do a lot on their hosted pages, without your own backend. If you want to automate things though, have user state based on payments, etc you will need a backend and a data store of some kind. But that could be an API that your static site points to.