microsoft / microsoft/aspire-samples
More advanced Dapr example
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 345
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 30
Description
I'm new to Dapr (and Aspire!) so I may be missing something, but I've read everything I can find without finding an answer. I'm starting a new project using microservices and I'd like to use Aspire and Dapr (and Radius?) with the goal of easy local development and production deployment to Kubernetes. I can't find any examples that use Radius. The examples I can find using Aspire and Dapr only use pubsub and state components; there's no more detailed examples using other components such as configuration. I'm also unclear on how to provide Dapr config for production. The AspireWithDapr example in aspire-samples uses the default pubsub or state component if they exist, otherwise the config for the in-memory component is created and used. So where/when do we provide the prod config? Will configuration components be added to Aspire.Hosting.Dapr or should we use AddContainer, AddDaprComponent and a yaml config file to add them to the AppHost? I'd really appreciate any guidance on the best practice and intended workflow here. I'm happy to provide feedback as well as this is something I'm currently working on.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the AspireWithDapr example mentioned in the issue and compare its pubsub and state component setup with the requested configuration and production scenarios. Done would be clear guidance or an expanded example covering advanced Dapr components, production configuration, and the intended Aspire, Dapr, and Radius workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- cloud, devops, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100