Automating a Payments Engine
summary
Claim: a vendor payments engine goes from a manual month-long deploy to 11 minutes by automating VM build and bootstrap via the bank’s skynet API, Chef cookbooks, Jenkins for WAR deploys, Inspec and Sensu for checks. The real technical blocker is a vendor that exposes only interactive KornShell installers, overcome with the expect library wrappers. Delivery uses co‑located three‑day sprints (dojos) over ~two months to onboard teams; databases remain manual and cultural backsliding after the dojo is a continuing risk.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:02Technical Overview
- 7:23Biggest Challenge
- 8:41Dojos
- 12:21What didnt work
- 14:50Behind the magic
- 17:27Conclusion
related talks
33mThe Road to Enable DevOps Within the Payment Industry
58mDEVOPS in a Multi-Banking World
32mBuilding Continuous Integration and Feedback
24mPromoting Automation of Build Work for Large-Scale Systems
40mAutomation is simple now using Devops
26mAutomate ALL the Things
49mAutomation in Deployment on Hybrid Hosting and Private Cloud Environments
22mFrom Code Commit to Production Within a Day