Bleeding edge engineering behavior is Apache Way
summary
FinTech teams adopt specific Apache Way practices: mailing-list archives and public repositories plus bug trackers for transparent history, a merit-based trusted committer path, and documented quickstart and developer guides. A payments platform at JP Morgan Chase is refactored into modularized microservices, isolating a vendor “red box” so the rest deploys independently. Outcome: 150+ distributed engineers ramp up faster, CI/CD stabilizes, tech debt narrows, scaling unblocks and business velocity increases during the pandemic.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:57Apache Software Foundation (ASF)
- 3:42Powered By Apache
- 5:16Apache Way Values
- 12:28ASF Openness/Collaboration
- 15:12Community Pyramid
- 18:01Pandemic & Industry Realization for Apache Way
- 20:20Fin Tech and Engineering Silos
- 21:26Well knowns issues
- 26:56Breaking Down Engineering Silos
- 29:23Transforming Siloed architecture with Apache Way
- 37:12Well knowns Results
related talks
46mFintech fear and loathing in banking
59mTech leadership, one year after
44mRoute to microservices the epic voyage of a fintech leader
49mBuilding a High-Performance Team is Everyone's Job
34m(Re)building an Engineering Culture: DevOps at Target
30mAn Evolutionary Approach to DevOps
33mSoftware development practices for companies that want to make an impact
51mBuilding a High-Performance Team is Everyone's Job