Getting started with internal open source
summary
Company moves from monolith to microservices and adopts an internal open source model where home squad/project squad ownership replaces silos; process uses kick-off design reviews, merge requests with required unit tests and living documentation, and a triage period after handover. Scale jumps from 4 to ~140 microservices in one department (about 900 company-wide), which creates bottlenecks that the model reduces by enabling cross-team contributions. Success depends on agreed standards, trust, frequent merges, and the ethos leave it better than you found it.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:42Change
- 5:34IRAs
- 6:47Big monolithic applications
- 8:15First project
- 9:57Serviceoriented architecture
- 11:00Team structure
- 12:23Microservices
- 15:47Organizational update
- 17:49New operating model
- 19:37How we work
- 24:19Guiding principles
- 26:45Why internal open source
- 36:44How to get the head start
related talks
28mInner Source
21mScaling Internal Collaboration with Open Source Operating Models
52mBottom-Up Open Source Culture
24mBuilding a Foundation for Open Collaboration
30mInnersource: open source collaboration patterns beyond public FOSS projects
23mLegacy, Open source, microservices and data architecture
23mThe Open Source Journey of the Most Unlikely Participant
43mFostering an Open Source Culture