✎ Key Insights in 30 Seconds
Architecture note: A practical account of how EPAS started with Nx and evolved toward a more flexible Angular micro-frontend structure as lending, disbursement, operations, and reporting modules grew.
Problem Context
EPAS had to support different institutions and configurable credit workflows without turning every change in lending, appraisal, disbursement, operations, or reporting into a coordinated rewrite of one frontend. The architecture also needed consistent authentication, navigation, form behavior, transaction state, and shared UI across business modules.
System topology
┌─────────────────────────────────────────────────────────────┐
│ Angular Shell (Host App) │
│ • Auth / Keycloak Session • Global Navigation • Routing │
└──────────────┬───────────────────────────────┬──────────────┘
│ (Webpack / Rspack Module Fed) │
┌──────▼──────┐ ┌──────▼──────┐
│ CRM MFE │ │ BPM MFE │
│ (Remote App)│ │ (Remote App)│
└──────┬──────┘ └──────┬──────┘
│ │
└───────────────┬───────────────┘
▼
┌─────────────────────────────────────────────┐
│ @shared/ui-lib & @shared/data-access │
│ • Dynamic Forms • Data Grid • Event Bus API │
└─────────────────────────────────────────────┘Architecture & Design
The first foundation used an Nx monorepo with Module Federation because it gave the team a clear workspace, shared libraries, and a consistent way to coordinate the Shell and Remote applications. As the product and delivery model became more flexible, that structure was redesigned and Nx was removed. The durable part was not the tool: it was the boundary between a host, independently delivered business modules, shared frontend contracts, and backend-owned workflow rules.
Key Technical Decisions
- 1Use Nx initially as a coordination and standardization tool, then remove it when its workspace conventions created more coupling than the product needed.
- 2Keep Module Federation and host/remote boundaries focused on independently delivered business modules rather than on a specific monorepo tool.
- 3Treat dynamic forms, task inboxes, transaction state, permissions, and reporting facts as explicit contracts between the frontend and backend.
- 4Keep shared UI and authentication behavior consistent while allowing lending, disbursement, operations, and reporting modules to evolve at their own pace.
Code & Configuration
export interface RemoteDefinition {
name: string;
entry: string;
exposedRoute: string;
capabilities: string[];
}
export const businessModules: RemoteDefinition[] = [
{
name: "credit-workflows",
entry: "/remotes/credit/remoteEntry.js",
exposedRoute: "/credit",
capabilities: ["forms", "approval", "disbursement"],
},
{
name: "operations-and-reports",
entry: "/remotes/operations/remoteEntry.js",
exposedRoute: "/operations",
capabilities: ["transactions", "audit", "reporting"],
},
];Verified repository evidence
architecture · direct
Built and evolved the Angular Micro-Frontend foundation for EPAS at NGV Group, including shared UI, lending and disbursement forms, transaction inboxes, workflow-facing screens, reporting surfaces, and private Kubernetes delivery.
↳ Private enterprise work: an Angular host with independently delivered CRM/BPM and credit-workflow modules. The early foundation used Nx, then the frontend structure was redesigned without Nx; the system includes dynamic forms, transaction inboxes, workflow and audit-facing UI, Kafka integration, and Jenkins CI/CD on on-premises Kubernetes.
Private Enterprise Work (NGV Group) ↗
Key Engineering Takeaways
- Architecture should preserve the useful boundary and be willing to discard the tool that no longer serves it.
- A workflow platform is shaped by business contracts—forms, tasks, approvals, transactions, and reports—not only by frontend composition.
- The best micro-frontend structure is the one that matches the product's actual ownership and delivery model.