Figure 1 illustrates a “mile-high” view of Subversion’s design.
On one end is a Subversion repository that holds all of your versioned data. On the other end is your Subversion client program, which manages local reflections of portions of that versioned data (called “working copies”). Between these extremes are multiple routes through various Repository Access (RA) layers. Some of these routes go across computer networks and through network servers, which then access the repository. Others bypass the network altogether and access the repository directly.