Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split KITT.Core project one per Bounded Context #118

Open
albx opened this issue Dec 28, 2024 · 0 comments
Open

Split KITT.Core project one per Bounded Context #118

albx opened this issue Dec 28, 2024 · 0 comments
Labels
management-tools All issues related to the web app which manages the channel refactor

Comments

@albx
Copy link
Owner

albx commented Dec 28, 2024

Actually the KITT.Core project contains all entities related to KITT (streamings, proposals, etc.).
Moving the project to .NET Aspire (see #109 ) and splitting each world in a separate bounded context (CMS, Proposals and others in the future) the KITT.Core project need to be splitted itself in order to become a class library per bounded context which contains all the "domain logic" related to the bounded context.

Up to now the BC identiefied are:

  • Cms (Streamings and contents in general such as talks and maybe video in the future)
  • Proposals
  • (in the future) Media management
@albx albx added enhancement New feature or request management-tools All issues related to the web app which manages the channel labels Dec 28, 2024
@albx albx added refactor and removed enhancement New feature or request labels Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
management-tools All issues related to the web app which manages the channel refactor
Projects
Status: Inbox
Development

No branches or pull requests

1 participant