Monorepos, Mainframes, and Modus Operandi Accepted
summary
American Airlines pilots a hybrid monorepo + mainframe workflow: a 19‑GB repo holding 15 apps, 41 shared packages, 90 npm deps and ~70 contributors. Pipeline uses GitHub/Coverity/Jenkins and TFS for .NET, with ISPW/Topaz and Z Advisor to push mainframe changes; XMatters for alerts and LaunchDarkly for feature flags. Results show ~330× faster multi‑app deploys, 250% more collaboration and ~4,200 hours reclaimed from deduplication, though tooling and scaling remain unresolved for broader adoption of mainframe DevOps.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:14Did you know
- 1:22Agenda
- 1:59Philip Kosovich
- 3:08American Airlines
- 4:34cynicism in IT
- 9:01culture change
- 9:54moving from projects to products
- 11:00managing teams
- 11:37product teams
- 11:56DevOps teams
- 12:26The mainframe
- 13:01DevOps
- 16:21Fear of failure
- 16:58Stack
- 17:35Plumbing
- 19:28Starting Comments
- 21:24Monorepos Structure
- 22:48Monorepos Workflow
- 23:15Deployment
- 24:09Breaking the Build
- 24:44Commit Process
- 25:44Results
- 27:26Challenges Risks
- 28:37Consulting
- 29:37Conclusion
related talks
26mMainframe DevOps Transformation Case Studies
34mMainstreaming the Mainframe - Taking the Agile and DevOps Journey
01h 00mReliability and speed by 'push to main' mentality
29mTaming the Hybrid Beast with DevOps
30mTwo Amazing Mainframe DevOps Transformation Case Studies
42mClosing the Agentic DevOps Loop with Microsoft and Moderne
40mMonorepo or Polyrepo: What's the Right Choice for You?
25mMicroservices, Monorepos, and the Efficient Build Processes