Kofi E. Ampaabeng

Selected Work

20 systems I have architected, built and run: enterprise platforms, consumer apps, and the tools and infrastructure behind them. 20+ years across regulated banking, data platforms and applied ML.

20
systems
6
enterprise
7
ML · LLM
20+
years

04 · Core banking

CWC Banking

Compliance is the architecture.

Core banking redesigned as configuration-as-code: products, postings, fees, rates and rules are versioned, effective-dated data over a small generic engine.

  • Enterprise

Surfaces

  • Web
  • Internet banking
  • On-prem
  • API
  1. 01Configuration-as-code — posting templates, product versions, fees, rates, limits and tax rules are versioned data; past rules are a point-in-time query.
  2. 02One ledger writer — every subledger hands a PostingRequest to one PostingService: request → template → journal.
  3. 03Transactional outbox — journals publish to Kafka from the same transaction that writes them.
  4. 04A full suite — deposits, loans, treasury, teller, fund management and trade finance across 57 modules and a 228-page operations portal.
  5. 05Internet banking — a customer portal for retail and corporate users: accounts, transfers, payments, mobile money, cards, term deposits and loans, with 11 modules each bank switches on or off.
  6. 06Observability and analytics — Micrometer metrics with OpenTelemetry tracing; an opt-in Cube.js and Evidence reporting layer.
  • 57 Gradle modules
  • 228 portal pages
  • 1 ledger writer
SurfacesWebInternet bankingOn-premAPI
CHANNELSDOMAINKERNELRECORDDOWNSTREAMPostingRequestsame transactionOperations portal228 pagesInternet bankingSubledgersdeposits · loansTreasury · trade · paymentsProduct configversioned, effective-datedPostingServicethe only writerPosting templatesJournalOutboxKafkaRegulatory reporting
Architecture, drawn from the codeServiceStoreModel usedModel trained hereFeedback
  • Spring Boot
  • Java 21
  • Kafka
  • Oracle · PostgreSQL
  • React