12/2024 – Present · Fullstack Developer (NGV Group) · Full-stack · Private enterprise work

EPAS — Enterprise Process Automation System

Configurable workflow platform for lending, disbursement, operations, and reporting across credit institutions

Repository ↗

What this system is for

EPAS is a private enterprise process-automation platform used across multiple credit institutions, including central-level organizations and People's Credit Funds. It brings configurable business processes such as lending, appraisal and approval, disbursement, post-disbursement operations, transaction handling, and operational or compliance reporting into one system. The public-safe story focuses on how those workflows become usable, traceable, and maintainable software.

What I owned

Translating lending and operational workflows into Angular micro-frontends, shared frontend foundations, dynamic forms, transaction inboxes, integration patterns, and delivery support across private on-premises environments. The architecture started with Nx, then evolved away from it when a more flexible structure fit the product and delivery needs better.

Details are intentionally redacted. The case study describes responsibilities and engineering decisions without exposing customer data, internal URLs, source code, or regulated figures.

Overview & Context

EPAS is a private enterprise process-automation platform used across multiple credit institutions, including central-level organizations and People's Credit Funds. It brings configurable business processes such as lending, appraisal and approval, disbursement, post-disbursement operations, transaction handling, and operational or compliance reporting into one system. The public-safe story focuses on how those workflows become usable, traceable, and maintainable software.

Problem & Constraints

The product had to express different institutions' business rules through configurable workflows while keeping forms, documents, approvals, transaction queues, audit history, and reporting facts consistent across business modules.

Business workflow surface

EPAS is not a collection of isolated screens: each module is part of a business chain with data, state, responsible actors, and reporting outputs.

  1. 01

    Lending, appraisal & approval

    Structured forms, supporting documents, task assignment, review stages, and approval decisions for credit workflows.

  2. 02

    Disbursement & post-disbursement operations

    The transaction and task surfaces needed to move an approved case into disbursement and continued operational handling.

  3. 03

    Operational, audit & compliance reporting

    History, status transitions, responsible actors, and reportable facts that help institutions inspect what happened in a process.

System Architecture

┌─────────────────────────────────────────────────────────────┐
│          Angular Host / Shared Frontend Contracts           │
│   Auth • Navigation • Forms • Tables • Transaction State    │
└──────────────┬───────────────────────────────┬──────────────┘
               │       Independently delivered modules        │
        ┌──────▼──────┐                 ┌──────▼──────┐
        │ CRM / Core  │                 │ BPM / Credit│
        │ Workflows   │                 │ Workflows   │
        └──────┬──────┘                 └──────┬──────┘
               │                               │
               └───────────────┬───────────────┘
                               ▼
        ┌─────────────────────────────────────────────┐
        │        Java Spring Boot Business Services   │
        │ Lending • Approval • Disbursement • Reports │
        └──────────────┬───────────────┬──────────────┘
                       │               │
        ┌──────────────▼──────┐ ┌──────▼──────────────┐
        │ Oracle / PostgreSQL │ │ Kafka • Redis • IAM  │
        └─────────────────────┘ └─────────────────────┘
  • Angular Micro-Frontend architecture with shared design libraries and flexible module delivery
  • Event-driven messaging with Apache Kafka and distributed cache with Redis
  • Oracle and PostgreSQL dual persistence with Keycloak OIDC authentication
  • On-premises Kubernetes cluster orchestration with ingress and health monitoring

Engineering Deliverables

  • Started the Angular Micro-Frontend foundation with Nx to establish shared conventions, routing, and shell-to-remote coordination.
  • Reworked the frontend structure later and removed Nx when a more flexible delivery model better matched the product's independent business modules.
  • Engineered shared component libraries for dynamic forms, custom data grids with virtual scrolling, pagination, and multi-file attachments.
  • Implemented lending and disbursement transaction inboxes with task dispatching, audit trails, and multi-tier approval flows.
  • Integrated frontend clients with Spring Boot REST services, Keycloak OIDC authentication, and Kafka event streaming.
  • Supported operational and compliance-facing reporting surfaces, then authored Jenkins declarative CI/CD pipelines for private Kubernetes delivery.

Engineering Signals & Outcomes

  • Configurable lending, disbursement & reporting workflow surface
  • Flexible frontend delivery across independent business modules
  • RBAC security with Keycloak and a repeatable private rollout path

Engineering Outcomes

  • A configurable workflow surface spanning lending, approval, disbursement, operations, and reporting.
  • A more flexible frontend structure that keeps business modules independent without treating Nx as a permanent constraint.
  • A public-safe engineering record that separates product responsibility from confidential business data.

Engineering threads behind the project

Each thread links to notes focused on one concrete decision or engineering problem.

Technologies & Tooling

Angular · Micro-Frontend · Java Spring Boot · Oracle · PostgreSQL · Kafka · Redis · Keycloak · Kubernetes · Jenkins

Related Engineering Notes