Skip to content
  • Home
  • About Me
  • Blog
  • Contacts
  • Home
  • About Me
  • Blog
  • Contacts
  • Home
  • About Me
  • Blog
  • Contacts
  • Home
  • About Me
  • Blog
  • Contacts

BrewUpErp

  • 1. The Brewery Domain
    • 1.1 Why Modular Monolith
    • 1.2 Repository Structure
    • 1.3 Bounded Contexts
    • 1.4 CQRS in BrewUp
    • 1.5 Event-Driven Architecture
  • 2. Governance
    • 2.1 Why Fitness Functions Matter
    • 2.2 Enforcing Module Boundaries
    • 2.3 Living Documentation
  • 3. Domain Modeling
    • 3.1 Aggregates
    • 3.2 Specification Tests
    • 3.3 Domain Events
  • 1. The Brewery Domain
    • 1.1 Why Modular Monolith
    • 1.2 Repository Structure
    • 1.3 Bounded Contexts
    • 1.4 CQRS in BrewUp
    • 1.5 Event-Driven Architecture
  • 2. Governance
    • 2.1 Why Fitness Functions Matter
    • 2.2 Enforcing Module Boundaries
    • 2.3 Living Documentation
  • 3. Domain Modeling
    • 3.1 Aggregates
    • 3.2 Specification Tests
    • 3.3 Domain Events

1.2 Repository Structure

This page is extremely important.

Explain:

* Solution layout
* Projects
* Modules
* Contracts
* Shared Kernel (if any)
* Infrastructure isolation

Add diagrams.

Use entity references for technologies:

* ASP.NET Core
* Blazor
* MongoDB
* RabbitMQ

You should visually distinguish:

* Domain
* Application
* Read Models
* Infrastructure
* Contracts

info@albertoacerbis.com

Twitter Github Github Github Strava
  • 2026 Alberto Acerbis. All Rights Reserved
  • Privacy Policy
  • Cookie Policy
  • Contacts
  • Credits
  • Privacy Policy
  • Cookie Policy
  • Contacts
  • Credits
  • Italiano
  • English