[[the following is still under construction]]

Benefits

• Power - You are free to implement your business logic and store your business data using any syntax, data-structure and algorithm your programming language supports: SQL, pure OO, functional, reactive functional, whatever. The Prevalent System pattern is orthogonal to that.

• ACID Transactions

• Persistence - Prevalent System state is persisted transparently without the need of a DBMS.

• Performance - There is no system architecture faster and more performance-scalable than System Prevalence, period. Queries on Prevalent Systems are 3 to 4 orders of magnitude faster than using a relational database, for example, depending on the RDBMS you choose to compare. Details below.

• Stability - System Prevalence is based on the simple and proven concepts of transaction logging and system state snapshots. That makes Prevalent System implementations straightforward and stable.

• Load Balancing

• Fault Tolerance - If one machine in your Prevalent System crashes, no big deal. The system will prevail.

• Local Mirroring - It is trivial to create local mirrors of any Prevalent System, so that your users can experience a rich user interface (not browser limited), without the need of clumsy remoting middleware such as CORBA, RMI or SOAP, and with zero latency for queries.

• Simplicity - The concept is so simple it actually enrages some people.

Applications

In stand-alone mode: Document editors, CAD / CAM / CAE, personal productivity apps, embedded apps, SCADA, devices, games.

In single server mode: websites, e-commerce, business systems.

In clustered server mode: Critical non-stop systems, heavy-duty websites.

In local mirror mode: Multi-user CAD / CAM / CAE projects, multi-user document editing, workflow, small business systems, multi-user games, sovereign apps.

How it Works

Let us now see exactly how each of the benefits above is achieved:

[Under construction]

Limitations

• All the business data in your system must fit in RAM. That is precisely the Prevalent Hypothesis.

[Under construction]

Problems

[Under construction]

Comparison to Traditional Database Architectures

[Under construction]