Objectivity/DB: Difference between revisions

Revision as of 08:00, 28 June 2024

Revision as of 19:09, 1 July 2024

Line 10:

==Architectural features==

Objectivity/DB operates as a [[distributed database|distributed database,]], providing a unified logical view across a network of databases. It employs a [[distributed computing]] model where client applications transparently communicate with simplified servers processes. This architecture enhances [[scalability]]<ref name="georgeTown">{{cite web|url=http://www.gsnmagazine.com/node/29210?c=cyber_security|title=Georgetown University taps Objectivity for Big Data research|date=May 2013|publisher=Government Security News|accessdate=December 1, 2014}}</ref> and [[reliability (engineering)|reliability]], supporting ingest rates exceeding one terabyte per hour while concurrently facilitating data fusion and query operations.<ref name="panasasPaper">{{cite web|url=http://www.panasas.com/sites/default/files/uploads/docs/panasas_objectivity_wp_lr_1065.pdf|title=Scaling Objectivity Database Performance with Panasas® Scale-Out NAS Storage|date=August 2011|accessdate=December 1, 2014}}</ref>

Objectivity/DB utilizes a distributed storage hierarchy, storing objects in logical clusters called containers within [[federated database|federated databases]]. Each object is assigned a unique 64-bit Object Identifier (OID) within a massive physical address space spanning millions of Terabytes. Notably, the largest reported deployment at SLAC's [[BaBar experiment]] stored over a petabyte of objects.<ref>[http://www.slac.stanford.edu/BFROOT/www/Public/Computing/Databases/proceedings/CIDR05.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>