Skip to main content

System Landscape: WepNG_MVC

Overview

WepNG_MVC is a monolithic solution acting as the central backend and legacy frontend for the WEP ecosystem. It is heavily interconnected with external libraries (EIT_NET, EIT_EOFFICE) and serves multiple actors (Internal Staff, Students, Public).

System Context Diagram (Mermaid)

Component Inventory

ComponentTypeResponsibilityDependencies
EITWEP.ModelClass LibraryCore Domain Model. Contains all business entities and logic.EIT_NET, EIT_EOFFICE
EITWEP.WepUtilsClass LibraryShared utilities, constants, and themes.EIT_NET
WepNG_APIWeb APICentral REST API for internal and external consumption.Core, Identity
WepNG_BOMVC AppBackOffice. Management interface for staff.Core, EIT_NET
WepNG_CRMMVC AppLegacy CRM. Mostly replaced by Zoho CRM. Retains Staff logic.Core, EIT_NET
WepNG_OMGTMVC AppOrder Management. Handling of student orders.Core, EIT_RES
WepNG_PublicMVC AppLegacy Website (Redirects/SEO Landing). Core site moved to DatoCMS/Vercel.Core, Caching
WepNG_AccessMVC AppAuthentication and User Access verification.Core, EIT_RES
WepNG_FormsMVC AppStandalone forms? (Needs deeper dive).Core
EITWEP.MaintenanceAppTool/AppLikely for background maintenance tasks or specific admin ops.Core, EOFFICE

External Ecosystem (New)

ComponentTechnologyResponsibilityIntegration
Public WebsiteNext.js (Vercel)Main marketing site and catalog.API (via WepNG_API)
Slick Price QuoteNext.js (Vercel)Internal Tool for Staff to create quick quotes. Replaces CRM Quote features.API (via WepNG_API)
Sales/Support CRMZoho CRMMaster system for Leads/Prospects (Migrated 2 years ago).Sync / API
CMSDatoCMSHeadless Content Management (Products, Articles).Webhooks / Build Time

Key Observations

  1. Dependency Hub: EITWEP.Model is the heart. Changing it risks breaking everything.
  2. External Coupling: The solution assumes the presence of ..\..\EIT_NET and ..\..\EIT_EOFFICE on the file system.
  3. UI Coupling: Usage of EIT.Web.Resources suggests shared JS/CSS assets managed externally.

🏗️ Infrastructure (On-Premise Datacenter)

The entire WepNG_MVC solution is hosted on-premise in the WEP Datacenter. The migration strategy relies on the existing virtualization layer to host Linux nodes.

LayerComponentDescription
HardwarePhysical Servers (Bare Metal)High-performance servers hosting the virtualization layer.
VirtualizationHypervisor(VMware ESXi / Microsoft Hyper-V / Nutanix) manages resource allocation.
Guest OS (Current)Windows Server VMsHosting IIS for the WepNG monolith (Legacy).
Guest OS (Future)Linux VMsHosting Docker/Kubernetes for .NET 8 services (Modern).

[!TIP] Co-location Strategy: Both Windows and Linux VMs will run side-by-side on the same Physical Servers. This maximizes hardware ROI and allows seamless network interoperability between Legacy (Windows/IIS) and Modern (Linux/Docker) components.

🚀 Deployment Topology (Current)

  • Web Tier: IIS on Windows Server VMs.
  • Data Tier: SQL Server (Separate Cluster).
  • File Storage: NAS / SAN mounted as drive letters.

📊 Reporting & Analytics Strategy

We are actively decoupling "Business Intelligence" from the Transactional Monolith.

  • Current: "Embedded BI" (Reports generated in C# inside WepNG_MVC).
  • Target: Zoho Analytics.
  • Pattern: Data is extracted (via ETL or API) to Zoho Analytics, where all Internal Reports, KPIs, and Dashboards are built. This removes the read-load from the main database and leverages a specialized BI engine.