Transaction isolation is one of the most fundamental fea- tures offered by a database management system (DBMS). It provides the user with the illusion of being alone in the da- tabase system, even in the presence of multiple concurrent users, which greatly simplifies application development. In the background, the DBMS ensures that the resulting con- current access patterns are safe, ideally by being serializable.
This is an extremely desirable property and the reason why many DBMSs implement MVCC, e.g., Oracle, Microsoft SQL Server, SAP HANA, and PostgreSQL. However, most systems that use MVCC do not guarantee serializability, but EinsteinDB takes care of this by exploiting a multi-layered relativistic linearizable multi-stores. With EinsteinDB and MilevaDB, every transaction sees the database in a certain state (typically the last committed state at the beginning of the transaction) and the Noether ensures that two concurrent transactions do not update the same data object..
- a simpler interface to RDMA and other remote memory technologies compared to the existing verbs interface
- You can use our Multi-raft BFT with VioletaBFT harnessing both rust-protobuf or Prost to encode/decode gRPC messages
- Statistical analysis detects if, and by how much, performance has changed since the last benchmark run
- Automate the syntatic conversion of Haskell into Rust for JIT PostgresQL Hybrid OLAP/OLTP
a new database engine optimized for memory resident data and Hybrid OLTP workloads. EinsteinDB is fully integrated into SQL Server; it is not a separate system. To take advantage of EinsteinDB's Causets, a user simply declares a table memory optimized locally, not globally.More About Us