Content delivery is one of the primary use cases for a Content Mangement system. When users are spread across six different continents, you must have an implementation that ensures timely access for all users – not just those in the local network. A typical scenario involves the database and primary Content Server deployed in the main North American or European datacenter with remote user groups scattered throughout the world. These remote offices often have limited network throughput, which makes it even more challenging.
Enter Branch Office Caching Services
Documentum has dealt with this scenario since its inception and has a myriad of options for streamlining delivery to users in geographically distributed locations or different departments, among them: remote content servers with distributed storage areas, federations with replication, and Branch Office Caching Services (BOCS). When we, as OnDemand Architects, looked at our customer needs and use cases, it became apparent that BOCS would be instrumental in providing remote users the experience they expected – which essentially boils down to application and content access on par with a local deployment.
Working with our customers in the real world, we have seen that web application access for remote users (whether via Webtop, D2, or xCP 2.0) is not signficantly impaired by the incremental increase in latency to return HTML/JS/CSS. The primary factor in application response and users’ perception of performance was the time it takes to transfer content during import, export, and checkin/checkout operations.