The Ten Minute Pitch

Three - A Networked Architecture

Perforce is built using a true, TCP/IP-based client/server architecture. The Perforce Server's repository sits on one central host, and client workspaces can be anywhere on the network -- across the office or across the ocean. Perforce's client/server architecture is key in providing efficient local workspaces and rich central metadata.

Local files. A Perforce client workspace consists of normal files sitting on the developer's local disk. That means for the important edit/build/test cycle, the developer works for the cost and at the speed of local disk storage. The cost of disk space continues to drop dramatically year by year, just as disk speed increases. Perforce banks on this trend.

Central metadata. Perforce tracks all client workspaces, as well as the evolution and contents of its repository, through a central metadata database. Because it is centrally located at the server, rather than scattered around in each client workspace, information about who has what, who is doing what, and what has been done is equally available to all users.

Streaming protocol. Perforce makes use of a well-tuned streaming message protocol for synchronizing client workspace and Perforce server repository contents. Designed to be efficient over long-latency networks such as WANs and the Internet, Perforce's protocol handles worldwide software development companies with ease.

[ Next - An Intelligent Core Database ]