Up to this point, we've built and connected services in the same solution and the same repository for our blog. This convenience and typical approach for .NET developers with mono-repos leads to this question and criticism of .NET Aspire:
You're right... that is a typical pattern for microservice development, placing services in separate folders in separate solutions with distinct source control repositories. Let's take a step away from our current demo, and build an API in a separate folder and a new solution using MongoDB to store posts. In fact, the completed sample code for this API isn't even in this repository. I moved it to https://github.com/csharpfritz/BigBadBlog.PostService
Let's assume I'm working on another team in conjunction with Arthur the Author to manage the content for the new blog engine. I'm building the PostService with MongoDB, my favorite NoSQL storage solution, in another repository and I'll expose the contents of the service using OpenAPI.