3 ms·
Databases really do push runtimes in such a way that I think it makes sense to urge folks to use a system level language, or something close to it. In particula
by switchbak 4y ago
Databases really do push runtimes in such a way that I think it makes sense to urge folks to use a system level language, or something close to it. In particular it'd be hard to cover concurrency (and parallelism) properly using vanilla CPython or JS, and I think that would impinge on the lessons learned.
That said, it'd be an interesting read on how to make a DB in pure Python.
- vira28 4y agoyou may be interested in this https://github.com/avinassh/py-caskdb https://github.com/avinassh/py-caskdb
- eatonphil 4y agoI don't normally think of Node and CPython as in the same performance bracket. Regardless, you can do some crazy things in Node. See these notes about Node and MySQL: https://github.com/tigerbeetledb/tigerbeetle/blob/main/docs/HISTORY.md https://github.com/tigerbeetledb/tigerbeetle/blob/main/docs/...
- deleted 4y ago[deleted]
- switchbak 4y agoIn this context I meant that the parallelism primitives are different than what you'll get in a systems level language, which might make teaching those parts unnecessarily awkward and probably the concepts less translatable to other runtimes. For sure they've got different performance profiles. Very impressive what your group was able to do with Node, and continuing on with Zig. It's got me interested in learning more.