White Papers (Architecture)

Overview of ClouSE Architecture

The high-level architecture of ClouSE is shown here:

ClouSE Architecture

The ClouSE transactional storage engine manages the following data:

  • a copy of the latest transaction log is stored locally
  • a persistent cache of recently accessed relational data is stored locally
  • relational and weblob data is stored in the cloud storage

The relational data is encrypted before it’s sent to the cloud storage provider to provide protection from accidental or malicious misuse. It’s also compressed to save network bandwidth and storage.

The ClouSE transactional storage engine implements functionality for transaction control, record-oriented access methods with fast key and range lookup, direct access to blob content, key range locking, and in-memory cache of recently accessed relational data for fast access.

The ClouSE handlerton implements the MySQL’s storage engine plugin interfaces to expose ClouSE to MySQL. The ClouSE is loaded into MySQL process as a pluggable storage engine.

For more information please read the full ClouSE documentation: The Cloud Storage Engine (ClouSE), v1.0