Can the sei db be used to like a regular db

Purpose of SeiDB

SeiDB is specifically designed for Sei’s blockchain architecture to tackle storage and performance challenges related to state management. It is not meant to serve as a general-purpose relational database.

Key Components

SeiDB has two main layers:

  1. State Commitment (SC): Utilizes a memory-mapped Merkle tree to store active chain state data, enabling quick access to transaction states and efficient Merkle hashing.

  2. State Store (SS): Optimized for full and archive nodes, it effectively handles historical queries.

Performance Optimizations

SeiDB significantly enhances performance compared to earlier storage solutions in Sei’s blockchain:

  • Decreases active state size by 60%
  • Lowers historical data growth by approximately 90%
  • Accelerates state synchronization by 1200%
  • Achieves a 287x increase in block commit speed
  • Doubles overall transactions per second (TPS) through faster state access and commits

Historical Data Handling

Although SeiDB is efficient for managing historical data, its design is tailored for Sei’s blockchain context and may not be suitable for general database functions outside that scope.

Flexibility and Backends

SeiDB supports multiple backend options like RocksDB, SQLite, and PebbleDB, offering some customization, but it remains primarily focused on blockchain-specific applications.

In summary, while SeiDB is equipped with robust storage capabilities tailored for blockchain use, it is not designed to operate as a conventional database. Its structure and optimizations are specifically aimed at resolving state management issues within Sei’s blockchain framework.