microsoft / microsoft/aspire-samples

Add samples for different patterns of composing services from multiple repositories into an AppHost project

Open
#35 1 comment 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-samples
Dominant language
C#
Stars
1.2k
Forks
345
Avg merge
3d 13h
Merged PRs (30d)
30

Description

From https://github.com/dotnet/aspire/issues/829

We should investigate how we can add some samples of various patterns that could be used to orchestrate projects and services from multiple repos rather than mono-repo. It's common to split up service ownership by team or simply to put them in their own repos.

Some patterns I imagine might emerge:

  • git sub-modules for service repos and a parent repo with the .sln file and AppHost project, if you want to build and run all services locally
  • Services published as container images that are then composed into an AppHost project as containers, if you don't want to build the services locally but you do want to run them locally
  • Dev-instances of services deployed to dedicated environments and/or locally that are then composed into an AppHost project as https://github.com/dotnet/aspire/issues/775, if you don't want to build or run the services locally

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Aspire issue #829 and the AppHost project context. Compare the three proposed patterns: git submodules, composed container images, and deployed or local dev instances. Done means adding representative samples that demonstrate the selected multi-repository composition patterns.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, docker, git
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.