Content deleted Content added
revert; you can run any applicaiton on Amazon EC2, nothing special about that |
|||
Line 9:
== Architectural features ==
Objectivity/DB is a [[distributed database]] that provides a single logical view across a federation of databases. It uses a [[distributed computing]] model that links a small software library with the client application. The client transparently communicates with remote servers that are functionally simpler than their equivalents in [[centralized database]] server architectures. There are lock, remote data transfer and query agent server processes. The distributed architecture helps make Objectivity/DB inherently scalable and reliable. It has sustained ingest rates in excess of one terabyte per hour while simultaneously supporting data fusion and query operations.<ref>[http://www.objectivity.com/pages/object-oriented-databases/building_high_performance_object_oriented_databases.html Building a High Throughput Data repository With High Query Performance] 2004</ref>
Objectivity/DB uses a hierarchy of storage constructs. Objects are stored in logical clusters called containers. The containers are stored in databases that are cataloged in a [[federated database]]. Every object has a unique 64-bit or 32-bit Object Identifier [OID] that is a composite logical structure. The physical address space limitation for a single federation is in the millions of Terabytes range. The largest publicized Objectivity/DB installation at SLAC's [[BaBar experiment]] stored over a Petabyte of objects.<ref>[http://www-db.cs.wisc.edu/cidr/cidr2005/papers/P06.pdf Lessons Learned from Managing a Petabyte] Jacek Becla and Daniel L. Wang, 2005</ref><ref>[http://www.slac.stanford.edu/BFROOT/www/Public/Computing/Databases/ BaBar Database]</ref>
|