How jezzsantos/saastack works
Core system components
• Frontend WebUI (labeled “Frontend”): Although marked “Under Construction” in the README, the codebase includes a ClientApp (in WebsiteHost/ClientApp) that represents the web UI layer.
• Backend APIs / Application Gateways: These include several API projects like “ApiHost1”, “AzureFunctions.Api.WorkerHost”, and “AWSLambdas.Api.WorkerHost”. They are providers of HTTP endpoints and integration delivery.
• Modular Domain Components (Subdomains): Modules such as Cars, Bookings, EndUsers, Organizations, Subscriptions, and UserProfiles are each implemented as their own set of projects. They represent the bounded contexts where Domain-Driven Design, Aggregates, Domain Events, and Event Sourcing are applied.
• Infrastructure Adapters and Technical Services: These include persistence layers (e.g., SQL, AWS, Azure adapters), integration adapters for third-party services (billing, identity, messaging, notifications), and adapters that abstract polyglot persistence. Also include common supporting libraries like Infrastructure.Eventing, Infrastructure.Hosting, and adapters under the “Tools” folder.
• Shared/Common Layers: These are the cross-cutting concerns such as Application.Common, Domain.Common, Infrastructure.Common, and shared libraries for logging, configuration, dependency injection, exception handling, and testing.
Relationships and interactions
• That each subdomain (Cars, Bookings, etc.) is composed of several layers: the Domain Layer (with aggregates, events, validations), the Application Layer (with services and handlers), and the Infrastructure Layer (with persistence, external adapters, API controllers). Use layered “onion” or “clean architecture” circles to indicate that the domain is at the center and is isolated from technical concerns.
• Test projects (unit tests, integration tests, architecture tests) as supporting components that validate the layers but are not directly deployed. You might include them to show that every major module is fully tested.
Architectural patterns and design principles
• Denote that the architecture is influenced by Clean Architecture, Onion Architecture, and Hexagonal Architecture – emphasize that the Domain Model is at the center, protected by application and then infrastructure layers.
• Mention that the template supports Domain-Driven Design (with Aggregates and Domain Events) and Event Sourcing. For example, attach a small “event trail” or “history” node near domain modules.
Relevant technology details
• That the system is built in .NET (Core 8+), using C#.
• Reference the common configuration using “appsettings.json” shown in configuration files across projects.
• CI/CD pipelines (e.g., GitHub Actions workflows with build.yml and deploy-azure.yml), which tie into cloud deployments.
• Optionally, show that integration with Azure and AWS is achieved via Infrastructure as Code (e.g., the “iac” folder for Azure ARM templates, SQL Server seed scripts, etc.).