Split Architecture & Inner Source. Let the developers spread their wings!
summary
HSBC runs over 300 Android developers, pushes 100 PRs a day to support apps in 30+ markets and claims Inner Source plus a Split Architecture cuts duplicate work. They extract foundational libraries (design system, networking, security) into separate repos with CI, publish journey features as versioned libraries to Nexus, and assemble per‑market apps via an appshell driven by Gradle flavors. Expect reusable UI components, clear contribution rules, PR templates and a maintainer workflow.
AI-written summary · about
chapters (5)
- 0:00Introduction to talk
- 1:56Why inner source matters
- 8:04Split architecture overview
- 19:23Building inner source community
- 31:31Q&A session
related talks
47mSecond space age: how to overcome the gravity of an internal development platform
47mVertical Architecture and Distributed Development - How Breuninger Scales
14mBootstrapping InnerSource at Airbus
47mHow Should Your OSPO Work with InnerSource?
28mBreaking Silos With InnerSource
26mDivide & Collaborate: Creating Scalable and Healthy Backstage Ba...
28mInner Source
41mUsing Boundary-Driven Development to beat code complexity