Is it good running fastapi and astro at the same project concurrently or better to separate it?

[merry root]

Hi @old raft. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

The knowledge sources do not contain information about running FastAPI alongside Astro in the same project. This is a question about architecture decisions involving FastAPI (a Python web framework), which is outside the scope of what I can address based on the available documentation.

What I can tell you is that Astro is designed to work with backend services via its REST API capabilities. For example, the Astro docs show integrating with external APIs (like PayloadCMS) by consuming their REST endpoints. [Payload CMS & Astro]

Astro also supports on-demand server rendering, which means it can handle some server-side logic natively without necessarily needing a separate backend. [On-demand rendering]

For a more informed answer about FastAPI + Astro architecture patterns, I'd recommend checking:

• The Astro community Discord
• The Astro backend services guide for general guidance on integrating backend services [backend services]

These resources may have community experience or examples relevant to your specific setup.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@old raft Kapa.ai is still learning and improving, please let me know how I did by reacting below.