Atomicity means that database operations are applied following a
“all or nothing” rule. A transaction is either fully applied or not
Consistency means that each transaction that modifies the database
takes it from one consistent state to another.
Drizzle: a database for the cloud.
Drizzle is a community-driven open source project that is forked
from the popular MySQL database. The Drizzle team has removed
non-essential code, re-factored the remaining code into a
plugin-based architecture and modernized the code base moving to
A database optimized for Cloud infrastructure and Web applications.
Design for massive concurrency on modern multi-cpu architecture
Optimize memory for increased performance and parallelism
Open source, open community, open design Scope
Re-designed modular architecture providing plugins with defined APIs
Simple design for ease of use and administration
Reliable, ACID transactional
Once a transaction is committed, it will remain so.
A referential constraint between two tables. Example: A purchase
order in the purchase_orders table must have been made by a customer
that exists in the customers table.
The Isolation requirement means that no transaction can interfere
An open source database that has spawned several distributions and
forks. MySQL AB was the primary maintainer and distributor until
bought by Sun Microsystems, which was then acquired by Oracle. As
Oracle owns the MySQL trademark, the term MySQL is often used for
the Oracle distribution of MySQL as distinct from the drop-in
replacements such as MariaDB and Percona Server.
Percona’s branch of MySQL with performance and management improvements.
A Storage Engine is a piece of software that implements the
details of data storage and retrieval for a database system. This
term is primarily used within the MySQL ecosystem due to it
being the first widely used relational database to have an
abstraction layer around storage. It is analogous to a Virtual File
System layer in an Operating System. A VFS layer allows an operating
system to read and write multiple file systems (e.g. FAT, NTFS, XFS,
ext3) and a Storage Engine layer allows a database server to access
tables stored in different engines (e.g. MyISAM, InnoDB).
Percona’s improved version of InnoDB providing performance,
features and reliability above what is shipped by Oracle in InnoDB.
This documentation is developed in Launchpad as part of the Percona Server 5.1.
If you spotted inaccuracies, errors, don't understood it or you think something is missing or should be improved, please file a bug.
For general inquiries, please send us your question and someone will contact you.