-
Marcio Barbosa authored
This commit introduces the necessary changes to decouple the write-ahead logging (WAL) from the storage layer. From now on, every change committed on the read-write node will be checkpointed immediately. The commit will only succeed if the WAL file containing the changes has been successfully delivered to the litelogd service. This service will then distribute the WAL file to all read-only replicas, which will apply the changes to their respective databases. [Milestone 1]
Marcio Barbosa authoredThis commit introduces the necessary changes to decouple the write-ahead logging (WAL) from the storage layer. From now on, every change committed on the read-write node will be checkpointed immediately. The commit will only succeed if the WAL file containing the changes has been successfully delivered to the litelogd service. This service will then distribute the WAL file to all read-only replicas, which will apply the changes to their respective databases. [Milestone 1]
README.md 775 B
LiteScale
LiteScale transforms SQLite into a cloud-native distributed database, inspired by Azure Hyperscale. It preserves SQLite's simplicity while enhancing scalability and durability by separating compute from storage and decoupling the write-ahead logging from the storage layer.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgements
This project uses SQLite, which is licensed under the Public Domain. See SQLite's License for more details.
This project uses the gRPC library, which is licensed under the Apache License 2.0. You can find the full text of the Apache License 2.0 at Apache License 2.0.