This document discusses the advantages and disadvantages of centralized version control systems (CVCS) and distributed version control systems (DVCS). It notes that while DVCS provide flexibility and independence, enterprises require a single source of truth for project consistency, security, and compliance. The document proposes a hybrid model using Perforce Helix that provides the benefits of both centralized and distributed version control by allowing developers to use native DVCS and Git tools locally while maintaining a centralized system for visibility, management, and security.

1. Single Source of Truth
in a distributed world
Sven Erik Knop

2. Centralised Version Control System (CVCS)
VCSLocal clients
Build
servers
Remote clients
Firewall

3. Advantages of CVCS
•Central security and authentication settings
•Overview of all projects
•Backup and maintenance
•Global workflow policies
•Simplified compliance checking

4. Disadvantages of CVCS
•Single point of failure
•Shared resource – shared performance
•One-size-fits-all (read “heavy”) approach to management
•No flexibility like working on the road
•Feels heavy and old-fashioned

5. Distributed Version Control System (DVCS)

6. Advantages of DVCS
• No network connection needed for common operations
• Automatic backup of repositories (multiple masters)
• Freedom
• No permissions necessary
• No oversight or control
• Different Workflows available, for example
• Commander / Lieutenant
• Pull requests
• Fast!

7. DVCS workflows
File Store Commander/Lieutenants Management Tool
Without oversight you’ll often find all types of workflows

8. DVCS in the Enterprise
•Requires management for
• User authentication and access management
• IP security
• Simplify reuse (why reinvent the wheel?)
• Compliance and traceability
• Common coding standards, build tools, test environments ...
•One place to find all projects and files?

9. Single Source of Truth

10. Why do we need a Single Source of Truth?
• Project consistency across all assets
• Code reuse & components
• Single administration & enhanced security
• For all teams around the globe

11. Requirements for Single Source of Truth?
•Single place for all types of documents of all sizes
•Common security and authentication settings
•Global access and visibility
•Flexible workflows
•Fast, reliable and not bogged down by build processes

12. Common security and authentication
•Your IP is the most important asset of your enterprise
•Can you authenticate every person accessing your IP?
•Can you guarantee that only authorized users have access?
•Can you protocol and audit any access?
•Can you protect your IP against insider threats?

13. Global access and visibility
Development
Team West
Design
Team West
Design
Team East
Headquarters

14. Single Source of Truth
with Perforce Helix

15. One version of all your assets
Contributors
Consumers

16. Distributed Single Source of Truth
Versioning Service
Proxy
Proxy
Edge Service
(humans)
D/R
Edge Service
(automation)

17. Hybrid workflow
•Direct connection increases visibility
• Which file(s) are you currently working on?
• Enables locking of digital (non-mergeable assets)
•Shelving and reviews for immediate feedback
•DVCS for increased mobility and flexibility
• Native DVCS and Git

18. Perforce Helix —
Unique Hybrid Version Management
Developers use the tools &
workflows they prefer
Business gets visibility,
scalability, and security
Git
Coder-preferred tools
Centralized
Control, visibility, security
Helix Local Instance
Enterprise-grade DVCS
PRODUCTIVITY
BUSINESS
REQUIREMENTS
VS

19. Security and Management
•Central access control for any file or asset
•Each change is protocolled
•Audit log keeps track of any access

20. Centralised vs Distributed?
•In the Enterprise:
• Many developers demand DVCS
• Still require central management
• Single Source of Truth for all source, assets and artefacts
•Hybrid version management
• Both distributed and centralised
• Single Source of Truth - with all the benefits of a distributed system

21. Sven Erik Knop
@p4sven
sknop@perforce.com
Q&A