Perforce Versioning Engine

P4D, the Perforce Server, is the engine powering Perforce's shared versioning service and file repository. P4D handles user requests and tracks development activity in its built-in database. There’s no need for special hardware other than storage for depot and database files.

Distributed Version Control Environment

Fast, Reliable Architecture

P4D is a self-contained program, simple to install and easy to upgrade and maintain. P4D is designed for high volume environments and is proven to support thousands of users and terabytes of data.

Built to Scale

Backed by flexible replication solutions that bring data closer to users, the Perforce versioning service supports cross-functional development teams, distributed work sites, and enterprise-grade automation and build infrastructure. Perforce’s unique content storage architecture gives you the control and flexibility to store any type of content without hurting performance.

Intelligent Branching

Perforce simplifies branch and merge operations with workflows based on the best practices we’ve seen over the last 15 years. Perforce branching lets you model the entire product lifecycle, from initial development through to release maintenance and customizations. Developers have several ways to manage development tasks and can merge with confidence. Release engineers can automatically guide change flow through tens of related product versions.

Easy Administration

P4D is self-contained and easy to install and administer—no third-party databases or application servers required. P4D supports user authentication for LDAP, Active Directory and other external data sources. If required for audit compliance, P4D can log individual file access to a log file. Perforce’s replication simplifies backup and disaster recovery. One part-time administrator can typically manage Perforce for hundreds of users, while a full-time admin can handle over 1,000.

Other Server Components

P4P, the Perforce Proxy, provides fast local access to versioned files at remote sites. With P4P, remote users can quickly access versioned content.

Perforce Proxy diagram

Low Overhead

Setting up a proxy requires minimal configuration and maintenance and no backups. Using a proxy is transparent to users, with no additional licensing costs. Thanks to this simplicity, most organizations deploy one or more proxies.

Lighter Shared Load

P4P offloads file transfer work from P4D, the shared versioning service. And proxies don’t just make end users happier: They can supply versioned files to build farms and other automated processes.

Perforce replication technology supports large user bases, remote teams, and automated processes. Perforce replicas have three behaviors supporting different use cases, driven by a few simple configuration settings.

Forwarding Replica

Need fast, local read-only operations? A forwarding replica (smart proxy) keeps you in the zone while relaying write activity to the shared versioning service. A forwarding replica in typical use can handle over 60% of user activity.

Build Replica

Implementing agile process automation such as continuous integration? Perforce build replicas support the largest build farms with no impact on the shared versioning service.

Standard Replica

Want peace of mind? A standard replica holds a complete read-only copy of the data kept in Perforce, providing a simple disaster recovery or backup solution.

P4Sandbox diagram

Git Fusion and P4Sandbox are seamless additions to the Perforce distributed version management environment. Git Fusion introduces powerful new capabilities for reusing and sharing code, while P4Sandbox gives you the speed and convenience of private local branching.

Git with the Enterprise

Git Fusion makes the Git experience more productive by giving teams powerful ways to combine elements from multiple repositories. Each site can have the full set of data it needs—from any combination of data in Perforce and Git.

Developers can collaborate without changing their use of Git. When they need to, they can take advantage of Perforce’s advanced suite of tools, including integrations with other applications, the ability to remap code on a grand scale, and tools to visualize file evolution and branch history. Release engineers can use proven solutions for managing product lifecycle “beyond the mainline”. And businesses can meet enterprise requirements for scalability, IP security, and visibility—the Perforce environment makes no sacrifices in compliance.

Private Local Branching and Offline Work

P4Sandbox lets you quickly start on new tasks or switch between tasks while automatically saving pending changes in the process and provides local versioning while you’re disconnected.