jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "Goals and non goals for Jackrabbit 3" by MichaelDürig
Date Thu, 16 Feb 2012 11:22:12 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "Goals and non goals for Jackrabbit 3" page has been changed by MichaelDürig:
http://wiki.apache.org/jackrabbit/Goals%20and%20non%20goals%20for%20Jackrabbit%203

New page:
=== Design principle ===
Best effort: everything might be corrupt at any time:
 * node types
 * child node existence
 * clients may not make '''any''' consistency assumptions

=== Goals ===
 * Pass TCK. But TCK might be adapted for invalid or edge cases.
 * Node type consistency on save and set type (including mixin). Inconsistencies occurring
do to write skew or degradation effects are acceptable though.  
 * Scalability: 
  * Read throughput: no degradation from current Jackrabbit 2, repeated read not slow, take
advantage of locality for random reads. '''TODO''': Needs further clarification
  * High write throughput across cluster nodes. 
  * Big lists of direct child nodes (10M)
  * Concurrent writes within single cluster node. '''TODO''': Needs further clarification
  * Big transactions (> 100000k nodes at 1kB each, cq5 content package)
  * Start up time < 1s
  * Number of nodes in repository (tar pm): 100M 
  * Number of nodes in shared cloud: 10T
  * 1G binaries with 2MB per binary => 2PB Repository size
 * Simple/Fast queries (i.e. through specialized indexes) (3ms)
 * Partitioning of observation. '''TODO''': Needs further clarification
  * Handling of recursive deletes: large number of NODE_REMOVED events vs. delete event for
specific properties in subtree.
 * Number of users: 200M / 20M per group
 * Full versioning model 
 * Flexible durability (depending on durability guarantees of back end)

=== Non goals ===
 * Node type consistency when node type definition changes
 * Consistency guarantees
 * Scalability:
  * Big property list
  * Same name siblings
  * Namespace remapping
 * Query index complete 
 * Fast move
 * JCR lock == sync
  
=== Maybe ===
 * Multi valued properties
 * Sharable nodes                       
 * Fast delete

Mime
View raw message