Plastic SCM is designed from the first day to grow with the team's needs, allowing server functions to be splitted among several server machines to achieve best performace.

Multiserver support

In the default configuration a single Plastic Server manages all repositories and workspaces, but the system is flexible enough to allow different layouts. Different repository and workspace servers can be configured to cooperate, enhancing overall system performance, reducing network usage, distributing storage and balancing CPU load. The following figure shows a scenario with multiple workspace servers working with a single repository server:

You can find more information on this feature at our Independent Workspace and Repository Servers Whitepaper or in chapter 6 on the Admin Guide.

Configurable Database Backend

To improve performance even more, Plastic SCM 2.0 introduced support for several database backends, allowing the administrator to fine-tune each server for maximum speed.

Many version control systems rely on their in-house data management implementation, while Plastic SCM uses relational database management systems for that purpose. Relying on those systems has many benefits, like fully transacted operations (ensuring data integrity), performance or well defined backup and restore procedures.

Plastic SCM can be configured to work with Firebird, SQL Server and MySQL database back ends, each of them having different features and benefits. Being able to work with different database back ends is not only good as added value for customers, it is good for software design. Our datalayer is currently ready to support other database systems like Oracle or PostgreSQL.