Commerce Bank Lending Application
A lending application that ingests, generates, and processes fixed-length and dynamic-length files exchanged with core banking systems, with secure SFTP transfers and end-to-end Apache Camel integration flows.
Stack
- Java
- Spring Boot
- Spring Security
- Apache Camel
- MySQL
- SQL Server
- Nomad
- Podman
- Consul
- Puppet
- Problem
- The lending workflow depended on exchanging structured files with multiple banking systems — PLSTRECS, CBA, AML, GL, DELUX, and ACH (NACHA) — each with its own fixed- or dynamic-length format. Processing needed to be reliable, auditable, and secure over SFTP.
- Approach
- Built integration flows in Apache Camel to parse and generate the various file formats, wired secure SFTP transfers, and implemented end-to-end processing on Spring Boot with Spring Security. Supported the move toward microservices and the platform setup using Nomad orchestrated through Puppet-based provisioning.
- Outcome
- Delivered reliable, secure file-processing flows across multiple core-banking systems and contributed to the platform's microservices modernization.
Context
The lending platform exchanges structured files with a range of core banking systems, each speaking a different fixed- or dynamic-length format. Files arrive and depart over SFTP, and every step has to be secure and auditable.
What I built
- Apache Camel integration flows to parse and generate fixed-length and dynamic-length files for PLSTRECS, CBA, AML, GL, DELUX, and ACH (NACHA).
- Secure SFTP transfer handling integrated into the end-to-end processing pipeline.
- Spring Boot / Spring Security services for the processing logic and access control.
- Platform and orchestration support for the microservices effort using Nomad, Podman, and Consul, provisioned with Puppet.
Results
Reliable, secure file processing across multiple banking systems, plus contributions to the platform’s ongoing move from a monolith toward microservices.
Want results like this for your team?
Get in touch