Pluck’s Data Technology layer keeps track of every bit of community content, from Reviews to Photos to Comments to Assigned Badges.
What it does for you
- Ensures your content is reliably stored and efficiently retrieved as needed
- Masks the complexity of Web-scale notions of flat file storage and caching layers
- Provides a record of user activity
- Tracks a vast array of contribution metrics for reporting
What’s in it
- Highly scalable indexed file system capable of meeting any load requirements
- 64-bit In-memory Data Caching Layer running on servers with as much as 256GB of RAM as well as high speed redundant physical data storage
- Fully searchable content via the Lucene Search Engine, supporting advanced field-level search as well as contextual phrase, wildcard and proximity queries
- Comprehensive record of every action taken on the system for activity and audit reports
- Complete set of downloadable reports covering all aspects of community member contributions
The Pluck Data Technology layer utilizes a variety of technologies and techniques to achieve high-performance storage with flexible retrieval. The majority of the data is stored in a scalable indexed file system (BDB).
Some data elements are also indexed for searches, and leverage technologies such as SQLite for sorting and filtering. Each type and layer of storage has its own caching system, which allows for full in-memory data access and queued writes to prevent file locking under load.
The storage servers utilize enterprise class 10K and 15K RPM SAS drives in RAID10 configuration to ensure world-class performance and reliability.
Pluck abstracts its processing technology and presentation technology layers from the underlying storage mechanics so that developers are free to invent and deploy Pluck functionality without concern for data integrity or performance.
The Data Technology layer also tracks activity and actions at a very granular level. This allows for an unrivalled level of auditing. Every action taken by community members and visitors is logged, along with a comprehensive set of contextual attributes for later reporting.