03 / U.S. Bank · Jul 2018 — Sept 2020
Ledger post APIs
Secure banking applications for customer services and transactions — 25+ Spring Boot APIs, with authentication and automated tests in the delivery path.
25+ REST APIs · 25%+ faster transaction workflows
services.internal/transfers
- Problem
- Customer transaction workflows were slow enough that people walked around the software. Security and tests were at risk of arriving as a later layer.
- Constraints
- Banking customer-service systems in Los Angeles. Existing authentication requirements.
- Decision
- Build 25+ REST APIs in Java and Spring Boot, refactor the slow paths, and keep authentication and automated tests in the delivery path.
- Tradeoff
- Architecture reviews ran long because they were for what could go wrong. Evenings belonged to a Computer Science master's at Texas Tech.
- How it was measured
- More than 25% faster transaction workflows — the résumé number. Ledger-post is an illustrative name for that U.S. Bank work.
Money has a temperature. You feel it in a transfer that posts and a screen that does not know yet.
At U.S. Bank that work was twenty-five-plus REST APIs for customer services and transactions — Java, Spring Boot, authentication on the way in.
The work was the hot path and the review of what could go wrong — not a later security layer. The degree happened after dinner.
- Java
- Spring Boot
- REST APIs
- Authentication
- Automated testing
- CI/CD