All work

A lending platform at a large bank

A large estate of thirty-odd repositories with strict security requirements and a rule that every change to data must be traceable — who made it and when.

What it is

A large estate: around thirty repositories — services, interfaces, shared libraries, environment configuration. Deals, offers, rates, tariffs, reference data, documents, approval processes.

Strict requirements for security, and for every change to data being traceable: who made it and when.

Engineering documentation

Worth mentioning separately: the internal documentation — a guide to the layers, a checklist for taking a new entity from start to finish. That answers the fear of being left alone with code nobody understands — and it is the same thing I bring to the projects I build for clients.

How it is built

A generalised view of the lending platform: interfaces, services, shared libraries and end-to-end auditingTwo interfacesmy areaOther interfacesother teamsDealsservice · my areaOffersservice · my areaRatesservice · my areaAbout 25 more repositoriesservices and librariesShared librariesapproval processes, models from BPMN · access: Keycloak, Kerberos · centralised configurationEnd-to-end change auditwho changed each record and when · domain entities separated from database entitiesDeliveryJenkins: security analysis, coverage · Helm values per environmentA generalised view of the lending platform: interfaces, services, shared libraries and end-to-end auditingTwo interfacesmy areaOther interfacesother teamsDealsservice · my areaOffersservice · my areaRatesservice · my areaAbout 25 more repositoriesservices and librariesShared librariesapproval processes, models from BPMNaccess: Keycloak, Kerberoscentralised configurationEnd-to-end change auditwho changed each record and whendomain entities separated from databaseentitiesDeliveryJenkins: security analysis, coverageHelm values per environment
Other case studies

Case studies and personal projects