How joeclack/thamco-events-management works
Main Components
• ThAmCo.Events Web Application – This ASP.NET Core Razor Pages project is the primary UI layer for managing events, guests, staff, and integrating with catering and venue functionalities.
• ThAmCo.Catering Web Service – An ASP.NET Core API that manages food items, menus, and food bookings.
• ThAmCo.Venues Web Service – A pre-built, external web service providing venue querying and booking capabilities.
• Database(s) – Multiple SQL Server databases (or logically separated schemas) underpin each service (using EntityFramework Core in both the Events and Catering projects, and the Venues project similarly).
• Identity & User Management – Embedded within the Events project using ASP.NET Core Identity (visible under the Areas/Identity folder).
Relationships and Interactions
• The Events Web Application acts as the central orchestration layer. It interacts with the Catering API for food-related operations (like booking food for events) and with the Venues service for venue reservation functions.
• Events → Catering: For operations such as food booking, retrieving menus, and food items.
• Events → Venues: For venue availability checks, reservations, and cancellations.
• Internal layers within each service should be depicted to illustrate the layered architecture:
• For example, in ThAmCo.Events, show the separation between the Presentation Layer (Razor Pages), Business Logic (Services such as EventService, GuestService, StaffService), and Data Access (ApplicationDbContext, EventsDbContext).
• Similarly, in ThAmCo.Catering, display the Controllers (handling API requests), Data Access (CateringDbContext), DTOs (data transfer objects) and Models (defining domain entities).
Architectural Patterns and Design Principles
• The solution is organized with clear separation of concerns (layered architecture). Each project uses controllers, models, DTOs, and a corresponding DbContext to encapsulate data operations.
• Many-to-many or one-to-many relationships (e.g., many-to-many between menus and food items in the Catering service, and one-to-many between events and guests in the Events application).
Relevant Technologies and Tools
• ASP.NET Core 6.0 for both web and API components.
• EntityFramework Core for O/RM and data management.
• MSSQL as the relational database backend.
• ASP.NET Core Identity for managing authentication/authorization in the Events project.