4 ms·
I recently created a database engine (exosql [1]), only query and no storage. It uses postgres-like foreign data wrappers to get all data. It's not valid for b
by dmoreno 8y ago
I recently created a database engine (exosql [1]), only query and no storage. It uses postgres-like foreign data wrappers to get all data.
It's not valid for big datasets, as it stores all in memory (or maybe it is?), but as a learning experience has been amazing to think and develop a real database: planner, executor, choose algorithms, implement features as lateral joins and so on.
I will definetly listen very carefully to these talks.
[1] https://gitHub.com/Serverboards/exosql https://gitHub.com/Serverboards/exosql
- zerr 8y agoAny books/lectures/articles you followed?
- dmoreno 8y agoI followed specially the postgres and sqlite documentations. For some specific areas I checked their source codes. But mainly I used explain from postgres as reference on what algorithms (seq scan, hash scan and do on) use for specific queries.
- suj1th 8y agoA similar learning experience for me was when I was exploring Apache Calcite. That again is only query, and no storage. It has a concept of 'adapters' which, I assume, is similar to the postgres-like foreign data wrappers you mention.