Barman, past, present, and future of a pioneer community project
summary
Project history from a July 2012 release to 13 years of development shows concrete outcomes: quarterly releases early on, a team that grows from three to about ten, then three junior hires in 2024 who deliver initial incremental backups and wall compression support for ZSTD/LZ4/C; cloud work adds S3/Azure/GCP object storage, EBS snapshot support and immutable storage plus basic GPG encryption. Roadmap lists export/import of self‑contained backups, better cloud integration, a lightweight barman service/API and evergreen/retention strategies.
AI-written summary · about
chapters (32)
- 0:00Introduction to Barman
- 1:49Why Barman was created
- 4:01Barman’s first release and early evolution
- 5:25Barman’s golden years 2012–2016
- 7:13Decline and community challenges
- 7:56Cloud integration begins
- 8:59EDB acquisition and team rebuild
- 10:00Cloud features expansion
- 11:04Barman Keep and modules
- 12:46Barman’s rebirth in 2023
- 13:51New team and incremental backups
- 14:34Compression and immutable storage
- 16:02Community interaction methods
- 17:27Documentation revamp
- 18:08Contributor guide plans
- 18:49Community contributions examples
- 21:21Pull request review process
- 23:57Internal release workflow
- 26:03Future plans overview
- 26:25Export and import backups
- 27:53Ransomware and immutable storage
- 29:20Encryption and Evergreen backups
- 30:48Barman Cloud incremental backups
- 31:53Postgres community collaboration
- 32:35Better cloud integration
- 33:40Barman service and API
- 35:49Three-tier backup strategy
- 39:08Q&A: Export import and PITR
- 40:57Q&A: PR review workload
- 43:29Q&A: Python 3.14 and speed
- 45:14Q&A: Development process
- 47:39Q&A: Evergreen backups
