Help: This page shows how the referencing vocabulary definitions are maintained and interlinked for controlled consistency of documentation. Click on the hyperlinks to see how the terms are defined within the Askemos architecture. moreā€¦ Tip: Remember the back-button!

This page has three main sections. (Note that the listings could be empty.)

  1. The first item displays a term, URL, text or picture.
  2. Followed by a (still unordered) listing of statements about this subject. (for details follow ">"-link)
  3. Separated by a horizontal rule a "reverse" listing of statements referring to this item in object position.
767 is a > software
927 description >

The "lower half" of the Askemos (or rather BALL) implementation, the agreement protocol and storage replication layer, is essentially a poor man's zookeeper.

Just not centralized.

This poor man's version was developed with a different design goals. First individual administration of each node. Second, the replica set in Askemos is a property of the object, while in zookeeper it's a global property defined by the configuration file. Otherwise small (interactive) datasets, frequent network partitions and otherwise failing peers. Specialised to byzantine paxos, no optimisations for streaming or otherwise combining operations and nowhere near as fast. (Though we tests only over wide area connections most of which are ADSL. Our network would not even transfer that much load.)

Besides the issue wt. choosing the replicates, zookeeper appears to be quite an huge dependency.

777 software utile > Paxos