More Related Content
Similar to Infographic: Perforce vs Subversion
GrowERP platform presentation based on OFBiz, git,gerrit, postgresql, nagios,...GrowERP platform presentation based on OFBiz, git,gerrit, postgresql, nagios,...Hans (J.C.) Bakker
Similar to Infographic: Perforce vs Subversion (20)
Infographic: Perforce vs Subversion
- 1. WHY SWITCH TO PERFORCE TODAY?
PERFORCE
SUBVERSION
VS
PERFORCE SUBVERSION
While Subversion’s upfront licensing costs are zero, it slows
productivity and forces you to spend valuable resources on code
management issues resulting from its suboptimal workflows, poor
scalability, and outdated functionality. The net loss in productivity is
far more costly than licensing proprietary SCM.
Perforce offers a compelling solution for those looking to regain
productivity lost to Subversion. It's a proven integrated platform,
optimized for Agile and continuous styles of product delivery.
Perforce’s professional services teams ensure that your migration to
Perforce is as low impact as possible.
CONCLUSION
Open source products such as Subversion are not “free.” They come
with hidden costs, such as lost productivity, delayed products, and
increased maintenance that have the potential to be an order of
magnitude more expensive than the savings in an upfront license fee.
We invite you to try Perforce for free
(for up to 20 users) at www.perforce.com.
Copyright © 2014 Perforce Software Inc.
All rights reserved.
All trademarks or registered trademarks used herein
are property of their respective owners.
PRODUCTIVITY
Easy merges,
straightforward
release management
Known issues
with merging
and branch
management
PERFORMANCE
Proven to be
dramatically
faster
Slow for
most common
operations
GLOBAL
TEAMSPerforce offers
a filtered
replication to
enable fast
global access
No built-in
caching or
replication
technology is
available
SECURITY
Built-in powerful
access control and
auditing facilities
Zero
out-of-box
NATIVE GIT
Supports
both central
workflow
and distributed
workflow
Offers only
traditional
central
workflow
SCALABILITY
Installations of
10,000 and
more users
and petabytes
of data
Struggles with
large repositories
and file sizes, limited
to about 250 users
and 1 TB of data