Home > Storage > PowerScale (Isilon) > Industry Solutions and Verticals > Media and Entertainment > Dell PowerScale OneFS and Perforce Helix Core > Helix Core architectures
You can deploy Helix Core in multiple ways. It has a massively scalable architecture and provides replication for high-performance development and builds.
Remote teams get faster access by using edge and replica servers. All your files are synchronized with a central server, including large binary files, large numbers of projects and users, and high-volume automation tasks (millions of transactions a day). Your global teams get it all at LAN speed—without compromising on security.
Helix Core and PowerScale are the only systems that you will never outgrow. They scale to support:
Global organizations can face challenges as they scale. Helix Core and PowerScale solve these issues, without the WAN wait.
The simplest deployment of Helix Core is a single server with a single depot, with a single set of users connecting to it.
The following figure shows a basic Helix Core configuration:
This configuration is fundamentally the simplest of Helix Core configurations. It has only a single site with a single server that all users access. All local user workspaces use a single depot.
The following figure shows a typical proxy topology:
In this configuration, file revisions that are requested by users at the remote site are first retrieved from the shared server (at Site 1) and transferred over relatively slow WAN links. Subsequent requests for the same file revision are delivered directly from the Helix Proxy (at Site 2) over the local site’s LAN. This architecture reduces both network traffic across the WAN and CPU load on the shared server.
The commit-edge architecture supports optimal performance for work groups at multiple geographic locations. At a minimum, the architecture has the following types of servers:
Because an edge server can handle read-only operations locally, the commit-edge architecture offloads a lot of processing work from the commit server and reduces data transmission between the commit and edge servers. This reduction greatly improves overall performance.