“API?” – How LendingHome Approaches “Legacy” Technologies
summary
LendingHome describes concrete fixes: an SQS-backed microservice Rainmaker that turns internal requests into FTP XML, a centralizer Grand Central that moves files via S3 and talks to many banks, and a jRuby/java FTP stack that proves more reliable than Ruby libs. Outcomes include 15 distinct FTP vendor integrations and five-minute setup, mandatory logging and saved-file archives, static IP requirements, streaming XML/CSV handling with Nokogiri and libXMLRuby, and a deployment that actually scales and reduces manual work.
AI-written summary · about
chapters (5)
- 0:00Introduction to legacy APIs
- 4:23Building your own interface
- 13:09Planning for failure
- 22:02Efficient processing
- 30:44Q&A and closing
related talks
43mRails services in the walled garden
49mIf I had it to do again
20marchitecture for event-enabling legacy core banking systems
18mWinning in the API economy
32mAirbnb's Great Migration: Service APIs at scale
31mSharing is caring: Building a modern microservice architecture helps everyone get ahead
23mAdopting APIs & Microservices at a Major Bank (Part 2)
32mRefactoring Legacy Apps with APIs and Messages