Skip to main content

🏛️ Architectural Statement: Response to Audit

To: External Technical Architect From: WepNG Engineering Team Date: January 2026 Subject: Architectural Maturity & Strategic Direction

Executive Summary​

This document serves as a response to the recent "audit" suggestions regarding microservices migration. It demonstrates that the WepNG platform's current monolithic architecture is a deliberate, strategic choice, not a legacy accident.

Our analysis confirms that a premature move to Microservices/Headless would introduce unjustified complexity without solving the core domain complexity.

1. The "Modular Monolith" Strategy​

We are pursuing a Modular Monolith approach. We have mapped the domain boundaries (docs/overview/domain_map.md) and are enforcing them via namespace separation before physical separation.

Why not Microservices now?​

  • Distributed Complexity: Our OrderMGT domain requires strictly consistent state transitions. Distributed transactions (Sagas) would jeopardize data integrity for little gain.
  • Operational Overhead: The team size does not justify the DevOps overhead of orchestrating 15+ services.

2. Rebuttal: The Headless/React Migration​

Regarding the suggestion to rewrite the frontend in React (Headless):

Status: REJECTED after detailed ROI analysis.

Reasoning:

  1. The "Kendo Trap": Our current MVC stack provides free server-side filtering/grouping. Replicating this in React would require ~9 months of boilerplate "glue code".
  2. Duplicated Logic: Validation rules would need to be duplicated (JS + C#), moving away from our "Single Source of Truth" in DataAnnotations.
  3. User Value: Operators value density and speed over "modern" SPA transitions.

See full analysis: docs/analysis/headless_migration_criticism.md

3. Specification Maturity​

We are not "undocumented". We have moved to a Hybrid Specification Strategy that exceeds standard industry practices:

  • Business Logic: Defined in Gherkin (Given/When/Then) for automated testability.
  • Lifecycle: Defined in Mermaid State Diagrams for strict transition validation.
  • Human Tasks: Defined in Cockburn Use Cases for UX clarity.

See: docs/guidelines/functional_strategy.md

4. Current Risk Management​

We are actively managing technical debt through a documented Anti-Patterns Registry. We know where the bodies are buried, and we have a plan for them.

  • See: docs/anti_patterns/

5. Tactical Acceleration: The "Sidecar" Pattern​

To address the need for modern .NET capabilities without a full rewrite, we have deployed the Shared Project Strategy (see ADR 005). This allows us to spin up .NET 10 "Sidecars" for new features immediately, sharing the data layer with the legacy monolith. This fundamentally changes the timeline from "Months of Rewrite" to "Weeks to First Feature".

Conclusion​

The WepNG platform is under active, controlled modernization. We invite you to review the docs/architecture/modules/ folder to see the depth of our current domain analysis.