py-caskdb VS gosqlparser

self plug: I wanted to learn how databases work internally, like how they store and retrieve data, build indexes, etc.

I built an educational KV store to teach someone to write a database from scratch. I have set up this project in TDD fashion with the tests. So, you start with simple functions, pass the tests, and the difficulty level goes up. There are hints if you get stuck. When all the tests pass, you would have written a persistent key-value store in the end.

link: https://github.com/avinassh/py-caskdb

link: https://github.com/avinassh/py-caskdb

If you like databases, you start exploring the internals and start writing one! There is no going back once you dig deep into storage internals, KV stores, and distributed systems.

plug: I made an educational project which can help you write a database in python, from scratch - https://github.com/avinassh/py-caskdb

Build your own disk based KV store

link - https://github.com/avinassh/py-caskdb

For learning, I built components of the database engine like an SQL parser, a file-based B+ tree, a log-structured merge-tree. And I planned to merge them into the simple database engine. But I paused the project due to the changes in life obstacles.

As part of my toy database development, I wrote a simple SQL parser as a dedicated library. I decided to share it with the community to get feedback and be useful 👉 github.com/krasun/gosqlparser.

Hey 👋 I recently finished writing a SQL parser for my toy database (in Go). I absolutely love the language and the simplicity it markets. I can share my story with Go. Let me know if you are interested.