Solution Topology

How the .NET solution separates orchestration, API, worker, core services, and tests.

RAG.AppHost   Aspire orchestration
RAG.Api       ASP.NET Core API + static UI
RAG.Worker    background ingestion loop
RAG.Core      shared domain, providers, storage, vector, EF Core
RAG.Tests     focused unit tests

This shape is useful because each project has a clear job:

• RAG.Api accepts user input and returns results.
• RAG.Worker performs slow ingestion work outside the request path.
• RAG.Core holds reusable logic and contracts.
• RAG.AppHost wires local infrastructure together.

The user uploads a document to the API, but the API does not process the book immediately. It stores the file, creates a metadata record, and returns quickly. The worker later picks up pending documents and runs extraction, enrichment, chunking, embedding, and vector indexing.

That asynchronous workflow matters because embedding a large PDF may take minutes. Blocking the upload request until all vectors are created would produce timeouts and a poor user experience.