A:
Because performance is primarily a result of efficient processes, not raw processing power. Caringo's major design goal was to dramatically reduce and simplify the processes underlying CAS. We eliminated unnecessary complexity in every element of the technology.
For example, where the file system and storage media interact, other CAS vendors rely on the existing hierarchical file systems to read and write information. In other words, their content-specific application is yet another additional layer atop a location-specific foundation. Performance suffers, and the more content, the bigger the hit. CAStor never goes through this extraneous location-to-content translation.
There are no standardized access methods for CAS. Some are built into applications, some, including the market leader, require that all requests and commands be made through a complex, proprietary API. This slows performance, limits multi-application support, introduces a slew of platform issues and can increase time to deployment. Caringo has developed the Simple Content Storage Protocol (SCSP), a very simple, straightforward application protocol using a subset of the familiar HTTP 1.1 protocol standard. SCSP uniquely supports content storage information, implementing only the necessary store, retrieve, get info and delete commands. Simply put, any user, application or development environment that can use the Internet can use CAStor.
|
|
email us © Copyright 2008 Caringo, Inc. All rights reserved.
