To keep global development synchronized, code submits are still committed to the master, but all other commands are entirely local. By storing metadata and content in a local environment, the new technology reduces data transfer and bandwidth usage between remote sites or between remote sites and a master, significantly speeding up developer workflows.

The new federation capabilities in P4D also enable replication of Git masters across a WAN  multisite Git teams operating behind a firewall can avoid the bottleneck of a central master.

Remote teams do not have to manage data that they do not require. This reduces WAN usage across the organization, shrinks hardware requirements for remote sites, and improves overall operational efficiency. Content filtering also enables an organization to limit visibility into critical chunks of code when security is a concern.

Continuous build, test, and integration transactions can be spread across multiple Edge services, while the master can be focused on serving user commits. This division of workload enables large organizations to scale development infrastructure with ease, while running the system on inexpensive hardware to further reduce costs.

"A multi-tiered architecture helps remove most versioning processes from the latency risks inherent in global networks, leading to quick and efficient workflows regardless of location," said Murtaza Amiji, director of product management at Perforce.

The firm has also announced the addition of a new version management capability  Parallel Sync  which allows users to transfer multiple files simultaneously and reduce overall workspace sync times./p>

P4 sync is the primary command for transferring updated files between a versioning depot and the development workspace. The new Parallel Sync capability enables the system to transfer multiple files simultaneously via the P4 sync command. This results in faster workspace creation for developers as well as automation tools, allowing teams to complete tasks faster.

"Parallel Sync is especially beneficial for teams practicing Continuous Delivery in highly automated environments, where Continuous Integration processes must obtain the latest code changes ahead of every test. Faster transfer of changes at each step of the Continuous Delivery pipeline speeds up the entire build-to-deploy process without any new investments," said Perforce.

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task.
However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Video

This month's Dr. Dobb's Journal

This month,
Dr. Dobb's Journal is devoted to mobile programming. We introduce you to Apple's new Swift programming language, discuss the perils of being the third-most-popular mobile platform, revisit SQLite on Android
, and much more!