How carlospeix/sabadostechhexagonal works
Project Type & Purpose
• This is an example (Ejemplo de arquitectura hexagonal) designed to demonstrate a hexagonal (or ports and adapters) architecture using .NET/C#.
• The project separates the core business logic from infrastructure concerns, promoting clean separation and easier testing.
Analyzing the File Structure
• Application (src/Application): Likely managing application-specific concerns, wiring dependencies, or orchestration.
• Model (src/Model): Contains the domain entities (Teacher, Subject, Grade, Parent, Secretary, etc.), configuration classes, and “UseCases” such as Notifications, along with ports subdirectories that define both Driving (e.g., INotifications) and Driven (e.g., INotificator, IRegistrar) interfaces.
• Persistence (src/Persistence): Implements infrastructure details, including data persistence mechanisms, database context, and migration files.
• Tests (src/Tests): Contains unit and integration tests for different parts of the application.
• Additional configuration files (e.g., .editorconfig, gitignore, etc.) support the coding standards and repository management.
Using the README for Additional Context
• The README succinctly states this is an “Ejemplo de arquitectura hexagonal” – emphasizing that the core aim is to illustrate the hexagonal architecture pattern.
• No extra dependencies or technical stacks are detailed, so focus on the hexagonal pattern as the key guiding principle.