SlideShare a Scribd company logo
 
What is Software Configuration Management? Configuration management tools track changes to development artifacts including but not limited to source code What are supposed to build or produce? What are we building or producing? What did we produce? Configuration management provides an effective, prudent, and logical function of project management that enforces a set of rules.  The goal of most developers is to set up the simplest system possible to achieve the desired result of control.
What development professionals look for in a SCM tool Platform support Scalability Ease of use Ease of acquisition Ease of administration Integrations with IDEs and other ALM tools Reporting and analytics Price Support for geographically distributed development teams Vendor stability
Forrester Wave™: Standalone SCM Solutions, Q2 ’07
Subversion is gaining share with development shops Base: 211 European application development professionals, Q4 2008 Base: 479 Americas application development professionals, Q1 2009  “ What SCM tools are commonly used in you application development organization?”
Subversion is popular with devs, especially Agile ones Base: 1298 application development professionals Source: Forrester – Dr. Dobbs Developer Technographics Q3 09 “ What is the primary SCM system you typically use?” (Choose one)
Why do developers choose Subversion?  Platform support Scalability Ease of use Ease of acquisition Ease of administration Integrations with IDEs and other ALM tools Reporting and analytics Price Support for geographically distributed development teams Vendor stability Price Capability  (quality + features) Substitution zone “ Cadillac” products “ Honda” products
Strategy 1: Remote access to a centralized repository Scales easily to support development sites of all sizes Provides a single source of truth Enables centralized administration Requires that the SCM solution perform adequately over WAN Can creates issues for commits, build, remote access This is the model most Subversion shops work with…
Strategy 2: Broker-mediated remote access to a centralized repository Improves performance in locations with poor network conditions Hub-and-spoke model can provide “network-near” performance Uses proxy and cache servers specific to the SCM solution Can also use generic proxy and cache servers Svnsync is a read only implementation of this solution
Strategy 3: Repository replication Periodic synchronization of repositories Requires reconciliation of contradictory changes Involves a period of time in which data is out of date Involves considerable hardware and administration expenditures SCM license costs tend to be higher “ Mastership” creates admin issues and bottlenecks
Strategy 4: Peer-to-peer communication  Read/write repositories broadcast updates Each repository is a full copy of “the truth” No mastership issues No single point of failure Gives distributed teams local read/write access for build/CI Requires robust and timely replication capabilities WANdisco is an example of a peer to peer model
Agenda What Is Total Economic Impact  TM  (TEI)? Approach The interviewed company  Key findings  Other benefits Conclusions
What is Total Economic Impact? Forrester’s TEI is the “Language of Value”  TEI ≠ TCO TEI provides a complete economic picture of tech purchase decisions  The four fundamental elements of TEI:  Benefits to the entire organization (not just IT) Costs Risk Flexibility
Review of existing relevant Forrester research Interviews with WANdisco’s SMEs In-depth interview with a Subversion MultiSite customer Construction of a financial framework — the model — around the interviewed company Construction of a case study — the narrative Forrester’s approach
Company interviewed for the study Global F500 manufacturer of electronic components Software development performed in 2 primary locations in the USA and Asia, with developers in 3 other locations in Europe, Asia and the USA. Support for over 400 software developers globally. Used a single Subversion repository located in the USA prior to deploying MultiSite. All software builds executed in the USA Decided to adopt Subversion MultiSite because: Asian developers were waiting for up to 2 days for builds to complete. Needed to provide redundancy for Subversion so there was no single point of failure. MultiSite customer since 2007 Has MultiSite running in two locations (USA and Asia) Usage grown from 170 to 520 active users Source code revisions grown from 500,000 to millions.
Key findings - Benefits Increased Asian developer productivity due to decreased latency Wait times for software builds to complete reduced from 2 work-days to 1.5 hours Builds can happen in parallel at every Subversion site 3 -year risk adjusted benefit of $194,161. Increases productivity due to improvement in bug fix rate MultiSite used to replicate bug tracking system. Bug fix rate improved by 30%. Bug tracking can happen in parallel at every Subversion site 3 -year risk adjusted benefit of $556,060 According to the development manager … “… builds were much more real time and people were able to more agilely track what changes are happening in the Subversion source tree, and it made the groups that were distant actually work better together when they didn’t have to wait for things to happen . . .”
Key findings – Benefits (cont.) Developer downtime avoided for Subversion system upgrades Developers can use alternate Subversion repository 3 -year risk adjusted benefit of $19,535 Reduced labor needed to perform security audits MultiSite allowed identification of dormant/orphan accounts, and to setup user access controls. Time to respond to security audits reduced from 5 to 2 days. 3 -year risk adjusted benefit of $6,749 Total 3 year risk adjusted benefit of $776,509
Key Findings - Costs Software license fees and maintenance fees Reflects standard list pricing for the customer’s installation as of September 2009. 3 year risk adjusted cost of $259,908 Servers for running MultiSite Does note require dedicated servers,  Assume 2 entry level servers. 3 year risk adjusted cost of $8,000 Implementation labor costs 2 week evaluation. Cutover from test to production required 2 hours downtime for 390 developers. 3 year risk adjusted cost of  $41,654 Ongoing support costs 1 hour of server maintenance monthly (12 hours/year) 3 year risk adjusted cost of $1,530 Total 3 year risk adjusted cost of $311,092
Key findings – Financial Summary, ROI and payback period Total 3 year risk adjusted benefits: $ $776,509  Total 3 year risk adjusted costs:  $311,092 3 year ROI: Risk adjusted: 150% Best case: 167% Payback period: Risk adjusted: 11 months Best case: 9 months Higher ROIs can be achieved with more sites and developers.
Other Benefits Avoid developer downtime while maintaining Subversion servers.  Load-balance between the servers.  Clearly identify the owners and originators of intellectual property. Identify active Subversion users and reduce the number of Subversion accounts. Substantially increase the number of software flavors that the company supports and releases. Reduce the labor effort required for security audits.
Conclusions Forrester found that organizations that use Subversion MultiSite can realize: Increased developer productivity because by providing developers with local access to source code repositories. Increase the bug fix rate, assuming the bug tracking system is replicated using MultiSite. Minimize or eliminate developer downtime during Subversion maintenance and upgrades.
Thank you Michael Speyer +1 617.613.6349 [email_address] www.forrester.com
 
Key Features Architecture Overview Distributed Agile Development Subversion Clustering Subversion High Availability System Requirements Summary Agenda
Peer-to-peer architecture with no single point of failure. Not master-slave or multi-master. Subversion repositories connected over a WAN synchronize automatically with each write operation. Developers at all locations experience LAN speed performance for both read and write operations. Built-in hot backup and automated recovery features eliminate downtime. Key Features
Replicator implemented as a transparent network proxy at each site. Client configurations don’t change. Subversion’s functionality doesn’t change. LAN-speed performance over a WAN due to a combination of : Unique Active-Active replication capability Network optimization features. Architecture
Subversion MultiSite supports distributed Agile by enabling: Continuous communication. Latest changes are available everywhere at LAN-speed. Merge conflicts are caught and fixed when they occur. Continuous build integration. Each site can perform builds and test locally with the latest code. Distributed Agile Development
Central servers can’t support Agile in large distributed environments. Slow networks cause remote sites to checkout and commit infrequently. Continuous build integration becomes impractical Proxy server solutions have the same network performance issues for commits and other writes. Remote sites can’t perform builds locally if write steps are involved. Distributed Agile Development
Same replication technology as Subversion MultiSite. Offload build process from development servers at large sites. Latest changes from development servers are available on build servers. Can be implemented in combination with Subversion MultiSite. Subversion Clustering
High Availability Ensures continuous hot backup of the primary server to one or more backup servers. Leverages the same automated recovery features as Subversion MultiSite and Subversion Clustering. Failover agent automatically redirects clients to backup server(s) in the event of a network outage or server failure.
Server Versions Supported Subversion server versions 1.3 and above are supported.   Backend Support: FSFS and Berkeley DB are supported. Supported Clients Subversion command line, SmartSVN, RapidSVN, TortoiseSVN, Subclipse, and any HTTP client that works with Subversion.  System Requirements WANdisco for Subversion will run in any J2SE 1.5 or above compliant Java runtime environment.  A minimum of 64 MB of RAM and 450MHz CPU is recommended for the server System Requirements
Unique technology allows distributed development teams to work as one at LAN-speed over a WAN, instead of working in silos. Dramatically reduces development time and cost. Peer-to-peer architecture with no single point of failure.    All servers can be monitored and administered from a single location.   Built-in continuous hot backup and self-healing capabilities eliminate risk. Makes full 24X7 operation possible in a globally distributed environment. Enables Agile development in a distributed environment.  Transparent implementation eliminates retraining. Summary
Customers

More Related Content

PDF
Engineering Software Products: 8. Reliable programming
PPT
Forrester Research on Globally Distributed Development Using Subversion
PPTX
uberSVN introduction by WANdisco
PDF
Forrester On Using Subversion to Optimize Globally Distributed Development
PPT
Why Svn
PPTX
Application Virtualization overview - BayCUG
PDF
Engineering Software Products: 5. cloud based software
PPTX
MDOP 2011
Engineering Software Products: 8. Reliable programming
Forrester Research on Globally Distributed Development Using Subversion
uberSVN introduction by WANdisco
Forrester On Using Subversion to Optimize Globally Distributed Development
Why Svn
Application Virtualization overview - BayCUG
Engineering Software Products: 5. cloud based software
MDOP 2011

What's hot (20)

PPTX
Modern Microservices Architecture with Docker
PDF
Flevy.com - Feasibility Study Template for Electronic Software Distribution
PPTX
App V
PPTX
Using SCCM 2012 r2 to Patch Linux, UNIX and Macs
PPTX
Techniques for Developing Systems in IT Management System
PPTX
Managing Updates with System Center Configuration Manager 2012
PPTX
Microsoft App-V 5.1 and Flexera AdminStudio Webinar
PPTX
Presentation on component based software engineering(cbse)
PPTX
Fundamentals of Deploy and Release
PPT
Vs2008 to improve Development
PDF
SCOM: The Unsung Hero of the System Center Suite April 24, 2013
PPT
Upgrade strategy
PPTX
VMware Horizon - news
PDF
Engineering Software Products: 10. Devops and code management
PPTX
Overview of Microsoft App-V 4.5
PDF
VMworld 2013: DR to The Cloud with VMware Site Recovery Manager and Rackspace...
PPTX
Mobile to mainframe - The Challenges and Best Practices of Enterprise DevOps
PDF
REX Meetic, Comment la qualité reflète-t-elle nos organisations ?
PPTX
MedV/AppV Overview
PDF
Continuous Application Delivery to WebSphere - Featuring IBM UrbanCode
Modern Microservices Architecture with Docker
Flevy.com - Feasibility Study Template for Electronic Software Distribution
App V
Using SCCM 2012 r2 to Patch Linux, UNIX and Macs
Techniques for Developing Systems in IT Management System
Managing Updates with System Center Configuration Manager 2012
Microsoft App-V 5.1 and Flexera AdminStudio Webinar
Presentation on component based software engineering(cbse)
Fundamentals of Deploy and Release
Vs2008 to improve Development
SCOM: The Unsung Hero of the System Center Suite April 24, 2013
Upgrade strategy
VMware Horizon - news
Engineering Software Products: 10. Devops and code management
Overview of Microsoft App-V 4.5
VMworld 2013: DR to The Cloud with VMware Site Recovery Manager and Rackspace...
Mobile to mainframe - The Challenges and Best Practices of Enterprise DevOps
REX Meetic, Comment la qualité reflète-t-elle nos organisations ?
MedV/AppV Overview
Continuous Application Delivery to WebSphere - Featuring IBM UrbanCode
Ad

Viewers also liked (10)

PDF
Alfresco - Forrester TEI Study
PDF
The Total Economic Impact of IBM Connections
PPTX
The ROI of Collaboration featuring research from Forrester
PPTX
The ROI on Intrusion Prevention: Protecting Both Your Network & Investment
PDF
Distributed Software Development Process, Initiatives and Key Factors: A Syst...
PPTX
ROI of Office 365: Forrester Total Economic Impact Summary
PDF
Global technology 2016 outlook
PDF
LUMA Digital Brief 012 - Market Report Q4 2016
PDF
Smartsheet erp users list
Alfresco - Forrester TEI Study
The Total Economic Impact of IBM Connections
The ROI of Collaboration featuring research from Forrester
The ROI on Intrusion Prevention: Protecting Both Your Network & Investment
Distributed Software Development Process, Initiatives and Key Factors: A Syst...
ROI of Office 365: Forrester Total Economic Impact Summary
Global technology 2016 outlook
LUMA Digital Brief 012 - Market Report Q4 2016
Smartsheet erp users list
Ad

Similar to Forrester Research on Optimizing Globally Distributed Software Development Using Subversion (20)

PPT
Make Subversion Agile
PPTX
Subversion Edge Overview
PPTX
Migrating from ClearCase
PPTX
Subversion and bug tracking
PPTX
Source control system SVN, QLIKVIEW & GIT
PPTX
DevOps Presentation.pptx
PPTX
Application Lifecycle Management with TFS
ODP
Introduction to Version Control
PPTX
Source control - what you need to know
PDF
SCM Migration Webinar - English
PPT
Os Nolen Gebhart
PDF
Codemash 2007 - Scm with subversion
PDF
The Replacement Rystem
PPTX
Beyond Scrum: Scaling Agile with Continuous Delivery and Subversion
PDF
Breakout Collaboration tools - Camille Reynders
PDF
.org to .com: Going from Project to Product
PPTX
Session on evaluation of DevSecOps
PDF
Hybrid Technology
PPT
SVN Usage & Best Practices
PPT
E crm m sc - warwick uni - crm solutions
Make Subversion Agile
Subversion Edge Overview
Migrating from ClearCase
Subversion and bug tracking
Source control system SVN, QLIKVIEW & GIT
DevOps Presentation.pptx
Application Lifecycle Management with TFS
Introduction to Version Control
Source control - what you need to know
SCM Migration Webinar - English
Os Nolen Gebhart
Codemash 2007 - Scm with subversion
The Replacement Rystem
Beyond Scrum: Scaling Agile with Continuous Delivery and Subversion
Breakout Collaboration tools - Camille Reynders
.org to .com: Going from Project to Product
Session on evaluation of DevSecOps
Hybrid Technology
SVN Usage & Best Practices
E crm m sc - warwick uni - crm solutions

More from WANdisco Plc (10)

PPTX
Supporting Financial Services with a More Flexible Approach to Big Data
PDF
Hadoop scalability
PPTX
03.13.13 WANDisco SVN Training: Advanced Branching & Merging
PDF
02.28.13 WANdisco ApacheCon 2013
PPTX
02.28.13 WANDisco SVN Training: Getting Info Out of SVN
PPTX
02.19.13 WANDisco SVN Training: Branching Options for Development
PPTX
Hadoop and WANdisco: The Future of Big Data
PPT
Subversion Zen
PPT
WANdisco Subversion Support Services
PPT
Subversion in 2010 and Beyond
Supporting Financial Services with a More Flexible Approach to Big Data
Hadoop scalability
03.13.13 WANDisco SVN Training: Advanced Branching & Merging
02.28.13 WANdisco ApacheCon 2013
02.28.13 WANDisco SVN Training: Getting Info Out of SVN
02.19.13 WANDisco SVN Training: Branching Options for Development
Hadoop and WANdisco: The Future of Big Data
Subversion Zen
WANdisco Subversion Support Services
Subversion in 2010 and Beyond

Recently uploaded (20)

PDF
CIFDAQ's Market Insight: SEC Turns Pro Crypto
PDF
Modernizing your data center with Dell and AMD
PPTX
Digital-Transformation-Roadmap-for-Companies.pptx
PDF
Dropbox Q2 2025 Financial Results & Investor Presentation
PDF
Building Integrated photovoltaic BIPV_UPV.pdf
PDF
Empathic Computing: Creating Shared Understanding
PPTX
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
PDF
Advanced methodologies resolving dimensionality complications for autism neur...
PDF
Encapsulation theory and applications.pdf
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
PPTX
Big Data Technologies - Introduction.pptx
PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
PDF
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
PDF
Per capita expenditure prediction using model stacking based on satellite ima...
PDF
Agricultural_Statistics_at_a_Glance_2022_0.pdf
PDF
Spectral efficient network and resource selection model in 5G networks
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PDF
cuic standard and advanced reporting.pdf
PDF
Network Security Unit 5.pdf for BCA BBA.
CIFDAQ's Market Insight: SEC Turns Pro Crypto
Modernizing your data center with Dell and AMD
Digital-Transformation-Roadmap-for-Companies.pptx
Dropbox Q2 2025 Financial Results & Investor Presentation
Building Integrated photovoltaic BIPV_UPV.pdf
Empathic Computing: Creating Shared Understanding
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
Advanced methodologies resolving dimensionality complications for autism neur...
Encapsulation theory and applications.pdf
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
Big Data Technologies - Introduction.pptx
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
The Rise and Fall of 3GPP – Time for a Sabbatical?
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
Per capita expenditure prediction using model stacking based on satellite ima...
Agricultural_Statistics_at_a_Glance_2022_0.pdf
Spectral efficient network and resource selection model in 5G networks
NewMind AI Weekly Chronicles - August'25 Week I
cuic standard and advanced reporting.pdf
Network Security Unit 5.pdf for BCA BBA.

Forrester Research on Optimizing Globally Distributed Software Development Using Subversion

  • 1.  
  • 2. What is Software Configuration Management? Configuration management tools track changes to development artifacts including but not limited to source code What are supposed to build or produce? What are we building or producing? What did we produce? Configuration management provides an effective, prudent, and logical function of project management that enforces a set of rules. The goal of most developers is to set up the simplest system possible to achieve the desired result of control.
  • 3. What development professionals look for in a SCM tool Platform support Scalability Ease of use Ease of acquisition Ease of administration Integrations with IDEs and other ALM tools Reporting and analytics Price Support for geographically distributed development teams Vendor stability
  • 4. Forrester Wave™: Standalone SCM Solutions, Q2 ’07
  • 5. Subversion is gaining share with development shops Base: 211 European application development professionals, Q4 2008 Base: 479 Americas application development professionals, Q1 2009 “ What SCM tools are commonly used in you application development organization?”
  • 6. Subversion is popular with devs, especially Agile ones Base: 1298 application development professionals Source: Forrester – Dr. Dobbs Developer Technographics Q3 09 “ What is the primary SCM system you typically use?” (Choose one)
  • 7. Why do developers choose Subversion? Platform support Scalability Ease of use Ease of acquisition Ease of administration Integrations with IDEs and other ALM tools Reporting and analytics Price Support for geographically distributed development teams Vendor stability Price Capability (quality + features) Substitution zone “ Cadillac” products “ Honda” products
  • 8. Strategy 1: Remote access to a centralized repository Scales easily to support development sites of all sizes Provides a single source of truth Enables centralized administration Requires that the SCM solution perform adequately over WAN Can creates issues for commits, build, remote access This is the model most Subversion shops work with…
  • 9. Strategy 2: Broker-mediated remote access to a centralized repository Improves performance in locations with poor network conditions Hub-and-spoke model can provide “network-near” performance Uses proxy and cache servers specific to the SCM solution Can also use generic proxy and cache servers Svnsync is a read only implementation of this solution
  • 10. Strategy 3: Repository replication Periodic synchronization of repositories Requires reconciliation of contradictory changes Involves a period of time in which data is out of date Involves considerable hardware and administration expenditures SCM license costs tend to be higher “ Mastership” creates admin issues and bottlenecks
  • 11. Strategy 4: Peer-to-peer communication Read/write repositories broadcast updates Each repository is a full copy of “the truth” No mastership issues No single point of failure Gives distributed teams local read/write access for build/CI Requires robust and timely replication capabilities WANdisco is an example of a peer to peer model
  • 12. Agenda What Is Total Economic Impact TM (TEI)? Approach The interviewed company Key findings Other benefits Conclusions
  • 13. What is Total Economic Impact? Forrester’s TEI is the “Language of Value” TEI ≠ TCO TEI provides a complete economic picture of tech purchase decisions The four fundamental elements of TEI: Benefits to the entire organization (not just IT) Costs Risk Flexibility
  • 14. Review of existing relevant Forrester research Interviews with WANdisco’s SMEs In-depth interview with a Subversion MultiSite customer Construction of a financial framework — the model — around the interviewed company Construction of a case study — the narrative Forrester’s approach
  • 15. Company interviewed for the study Global F500 manufacturer of electronic components Software development performed in 2 primary locations in the USA and Asia, with developers in 3 other locations in Europe, Asia and the USA. Support for over 400 software developers globally. Used a single Subversion repository located in the USA prior to deploying MultiSite. All software builds executed in the USA Decided to adopt Subversion MultiSite because: Asian developers were waiting for up to 2 days for builds to complete. Needed to provide redundancy for Subversion so there was no single point of failure. MultiSite customer since 2007 Has MultiSite running in two locations (USA and Asia) Usage grown from 170 to 520 active users Source code revisions grown from 500,000 to millions.
  • 16. Key findings - Benefits Increased Asian developer productivity due to decreased latency Wait times for software builds to complete reduced from 2 work-days to 1.5 hours Builds can happen in parallel at every Subversion site 3 -year risk adjusted benefit of $194,161. Increases productivity due to improvement in bug fix rate MultiSite used to replicate bug tracking system. Bug fix rate improved by 30%. Bug tracking can happen in parallel at every Subversion site 3 -year risk adjusted benefit of $556,060 According to the development manager … “… builds were much more real time and people were able to more agilely track what changes are happening in the Subversion source tree, and it made the groups that were distant actually work better together when they didn’t have to wait for things to happen . . .”
  • 17. Key findings – Benefits (cont.) Developer downtime avoided for Subversion system upgrades Developers can use alternate Subversion repository 3 -year risk adjusted benefit of $19,535 Reduced labor needed to perform security audits MultiSite allowed identification of dormant/orphan accounts, and to setup user access controls. Time to respond to security audits reduced from 5 to 2 days. 3 -year risk adjusted benefit of $6,749 Total 3 year risk adjusted benefit of $776,509
  • 18. Key Findings - Costs Software license fees and maintenance fees Reflects standard list pricing for the customer’s installation as of September 2009. 3 year risk adjusted cost of $259,908 Servers for running MultiSite Does note require dedicated servers, Assume 2 entry level servers. 3 year risk adjusted cost of $8,000 Implementation labor costs 2 week evaluation. Cutover from test to production required 2 hours downtime for 390 developers. 3 year risk adjusted cost of $41,654 Ongoing support costs 1 hour of server maintenance monthly (12 hours/year) 3 year risk adjusted cost of $1,530 Total 3 year risk adjusted cost of $311,092
  • 19. Key findings – Financial Summary, ROI and payback period Total 3 year risk adjusted benefits: $ $776,509 Total 3 year risk adjusted costs: $311,092 3 year ROI: Risk adjusted: 150% Best case: 167% Payback period: Risk adjusted: 11 months Best case: 9 months Higher ROIs can be achieved with more sites and developers.
  • 20. Other Benefits Avoid developer downtime while maintaining Subversion servers. Load-balance between the servers. Clearly identify the owners and originators of intellectual property. Identify active Subversion users and reduce the number of Subversion accounts. Substantially increase the number of software flavors that the company supports and releases. Reduce the labor effort required for security audits.
  • 21. Conclusions Forrester found that organizations that use Subversion MultiSite can realize: Increased developer productivity because by providing developers with local access to source code repositories. Increase the bug fix rate, assuming the bug tracking system is replicated using MultiSite. Minimize or eliminate developer downtime during Subversion maintenance and upgrades.
  • 22. Thank you Michael Speyer +1 617.613.6349 [email_address] www.forrester.com
  • 23.  
  • 24. Key Features Architecture Overview Distributed Agile Development Subversion Clustering Subversion High Availability System Requirements Summary Agenda
  • 25. Peer-to-peer architecture with no single point of failure. Not master-slave or multi-master. Subversion repositories connected over a WAN synchronize automatically with each write operation. Developers at all locations experience LAN speed performance for both read and write operations. Built-in hot backup and automated recovery features eliminate downtime. Key Features
  • 26. Replicator implemented as a transparent network proxy at each site. Client configurations don’t change. Subversion’s functionality doesn’t change. LAN-speed performance over a WAN due to a combination of : Unique Active-Active replication capability Network optimization features. Architecture
  • 27. Subversion MultiSite supports distributed Agile by enabling: Continuous communication. Latest changes are available everywhere at LAN-speed. Merge conflicts are caught and fixed when they occur. Continuous build integration. Each site can perform builds and test locally with the latest code. Distributed Agile Development
  • 28. Central servers can’t support Agile in large distributed environments. Slow networks cause remote sites to checkout and commit infrequently. Continuous build integration becomes impractical Proxy server solutions have the same network performance issues for commits and other writes. Remote sites can’t perform builds locally if write steps are involved. Distributed Agile Development
  • 29. Same replication technology as Subversion MultiSite. Offload build process from development servers at large sites. Latest changes from development servers are available on build servers. Can be implemented in combination with Subversion MultiSite. Subversion Clustering
  • 30. High Availability Ensures continuous hot backup of the primary server to one or more backup servers. Leverages the same automated recovery features as Subversion MultiSite and Subversion Clustering. Failover agent automatically redirects clients to backup server(s) in the event of a network outage or server failure.
  • 31. Server Versions Supported Subversion server versions 1.3 and above are supported. Backend Support: FSFS and Berkeley DB are supported. Supported Clients Subversion command line, SmartSVN, RapidSVN, TortoiseSVN, Subclipse, and any HTTP client that works with Subversion. System Requirements WANdisco for Subversion will run in any J2SE 1.5 or above compliant Java runtime environment. A minimum of 64 MB of RAM and 450MHz CPU is recommended for the server System Requirements
  • 32. Unique technology allows distributed development teams to work as one at LAN-speed over a WAN, instead of working in silos. Dramatically reduces development time and cost. Peer-to-peer architecture with no single point of failure. All servers can be monitored and administered from a single location. Built-in continuous hot backup and self-healing capabilities eliminate risk. Makes full 24X7 operation possible in a globally distributed environment. Enables Agile development in a distributed environment. Transparent implementation eliminates retraining. Summary

Editor's Notes

  • #3: “ Principles of Configuration Management”, M. A. Daniels, 1985