Caringo

FAQ »
Reference info & CAS »
Caringo & CAS »
Transparent scalability »
No dedicated nodes »
Content Integrity Seal »
HTTP-based interface »
Real-time access »
How CAStor works »
Upgradeable hash »
Commodity vs. custom »
Ships on USB key »
Improved performance »

Q: Does CAStor have dedicated nodes for specific functions?

A: Thanks to its fully distributed architecture, CAStor continuously redirects system processing and data streams to individual nodes based on profile, capacity and availability — on a moment-by-moment basis. Cluster-wide network performance, efficiency and scalability are organically optimized on an ongoing basis.

CAStor's truly distributed nature eliminates the single point of failure. It does not require dedicated nodes for access or gateway functions or to store indexes or repositories. All nodes run the same code base. Non-stop operation and persistent information access are baseline CAStor functionality. This same architecture enables individual disk management and healing as fully autonomic functions — no intervention or predefinition required.

4 of 12