How bhaktarout038/evolutionary-architecture-by-example works
Major System Layers and Components
• Separate the system into logical components (or modules) such as:
– Contracts Module (designed as a rich Domain Model)
– Passes Module (designed as an Active Record, with mostly CRUD style logic)
– Offers Module (with minimal business logic; candidate for Active Record)
– Reports Module (implemented as a Transaction Script)
• In addition, you need to show the infrastructure pieces such as the in-memory event bus (in earlier chapters) and the external messaging (e.g. RabbitMQ) that emerges in the microservices extraction phase (Chapter 3).
Evolutionary Chapters
– Chapter 2: Modules Separation – show multiple projects (e.g. Fitnet.Contracts.Api, Fitnet.Contracts.Core, Fitnet.Passes.Api, Fitnet.Reports) with the modules now isolated in distinct deployable units (or code bases). Emphasize maintainability through separation of concerns.
– Chapter 4: Tactical Domain-Driven Design – zoom in on a complex module (for example, Contracts) and display its internal DDD layers. Show aggregates, entities, value objects, and domain events. Emphasize that while the system remains evolutionarily built, this domain is now modeled using tactical DDD.
Architectural Patterns and Technologies
– “Active Record” next to Passes and Offers modules (indicating CRUD centric design)
– “Domain Model” inside the Contracts module (alongside tactical DDD elements)
– “Transaction Script” near the Reports module
• Technology references where it makes sense:
– .NET 8, Docker, Fluent Validation, MediatR, EF Core and Dapper for instance.
• Optionally, mention that the solutions use static code analysis and integration tests (e.g. Tools like SonarAnalyzer) to enforce design quality.