gregsadetsky
Joined 16 years ago
Joined 16 years ago
Are you still going to use dqlite after this experience, or has it shaken your confidence in it? Also what’s been your experience with microk8s itself - I hadn’t heard of it before
IMHO support for transactions is a pretty important dividing line. Some engines support full SQLite transactions while others - like rqlite - don't officially support BEGIN/COMMIT [0], which matters if you rely on multi-statement transactions.
A friend/colleague has been building a pure-Python client for dqlite [1] (DB-API and SQLAlchemy), which may interest folks here. dqlite has full support for transactions, and like rqlite doesn't have external dependencies (ie no S3/Consul).
No knock on rqlite or any other engine - dqlite has warts too [2].
[0] https://rqlite.io/docs/faq/#does-rqlite-support-transactions
[1] https://github.com/letsdiscodev/python-dqlite-dbapi
[2] https://github.com/canonical/dqlite/issues/882 opened by my friend, https://github.com/canonical/dqlite/issues/908 , https://github.com/canonical/dqlite/issues/912 opened by me
---
Cofounder of a web mapping startup acquired by Apple.
Received awards from the US Coast Guard and the Governor General of Canada for creating a map that helped rescue 1,700 people during Hurricane Harvey.
---
Currently refurbishing laptops with robots! https://www.reviserobotics.com/ (YC W25)
Also working on Disco, an open source self-hosting software: https://disco.cloud/
See my talk about it at the Recurse Center: https://youtu.be/z2lP7C8VT6M
And this (slightly less chaotic) Devtools FM episode: https://www.youtube.com/watch?v=Xr3JJpbCRP0
---
And even more stuff that's wildly out of date - https://greg.technology • https://tandy.link/s/greg.technology