The Fallacies of Distributed Computing are a set of common but flawed assumptions made by programmers when first developing distributed applications. The fallacies are summarized as follows:
The network is reliable.
Latency is zero.
Bandwidth is infinite.
The network is secure.
Topology doesn't change.
There is one administrator.
Transport cost is zero.
The network is homogeneous.
A term to describe a uniquely identified set of object types and records sharing a single 'base' revision and Replica identifier
A database contains multiple Records
Has one: uuid
An instance of a database. Replicas are expected to contain all Changesets from any other replica they have been synchronized with, but those Changesets are not guaranteed to be in the same sequence on each replica
A changeset contains "old" and "new" versions of a set of database "Records", they can be of any Record Type.
Has one: source_uuid, sequence_no
Has many: changes
An entry in a changeset. Contains all the updates to a given record for this changeset
A Record is composed of zero or more Attributes and a universally unique identifier. Each record is categorized into a Record Type.
Has many: attributes
A Record Type is a category or "bucket" for zero or more records applications may define specific behaviours for Records of a certain Record Type, but Prophet does no more than to tag Records with a Record Type. Record Types are uniquely identified with a textual name and a UUID
Has one: textual label, uuid
A key-value pair on a Record.
Has one: key, value
A Conflict occurs when a Changeset is being applied and the current state of a Replica meets any of the following criteria:
The Replica already contains a record marked as "created" in the changeset
The Replica doesn't contain a record marked as "deleted" in the changeset
The Replica doesn't contain a record marked as "updated" in the changeset
The Replica contains a record marked as "updated" in the changeset, but the current state of the properties on the record does not match the "old" state of the record in the changeset.
When the local Replica
Exporting is the act of cloning a replica. The replica uuid (which is its identity) remains the same. An exported replica is useful for copying to another machine or USB stick, so that other people may pull your changes.
Publishing a replica just export it to another machine, usually over ssh.
Exporting or publishing to an existing replica just updates that replica, it does not perform a merge, since the replica uuid is the same for both copies.
Pushing and pulling merge changes from two different replicas. Pushing to or pulling from an empty replica creates it and assigns it a new replica uuid.
A (possibly read-only) data store that is not a Prophet replica (such as RT or Twitter). A Prophet replica can act as a gateway to a foreign replica.
Too many things get called records
Revision is a term from version control. the backing store may describe it but it's not a Prophet term
To install Prophet, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Prophet
CPAN shell
perl -MCPAN -e shell install Prophet
For more information on module installation, please visit the detailed CPAN module installation guide.