It seems marginally more convenient for a large team to have a unified front/backend and people seem to like sveltekit, but it doesn't personally bug me to have the two separated. I could also see advantages to typescript/prisma/zod for instance over sqlalchemy and pydantic; pydantic improves python a bit along with mypy/pyright but typing is still very much hacked-in. It also seems like I'd increase my hosting bill a bit, both because SSR shifts work to the server and because workers or similar services generally have markups over a VPS. Thanks :)
Most of the app can be statically built, first rendered on the server and then cached on a CDN as static files. Then certain rerenders and calls can be clientside and others can go through the server if needed.
It shouldn't just be a fashion choice, but a measured analysis. Like what is on your backend and what is on the edge, how would consistency work, what are the regional considerations, etc.
I feel like asking which infra to build without knowing the app is putting the cart before the horse. A dashboard is different from a chatbot is different from a marketing site is different from a graphics app, etc., and each has different architectural considerations.
Are you asking what was popular last year, or advice on what should be done today (2025)?