Depends on what you you need that backend to do, no?
The backend part of the framework is typically a BFF (Backend for Framework). Anything that has considerable domain logic would be its own service.
The backend part of the framework is typically a BFF (Backend for Framework). Anything that has considerable domain logic would be its own service.
Comments
Anyway, that part now involves routing, SSR/ISR, server actions, built on image optimization, and more niche stuff like OG image generation. That's a lot of concerns.
Tying that to a specific client side framework is perhaps the issue, which Astro tries to solve for.
BFFs are fine if that’s really all they do