7 ms·

Same idea as https://github.com/rqlite/rqlite https://github.com/rqlite/rqlite I presume but in rust vs go?

edoceo 5y ago
I came here to mention rqlite too. It's awesome, and non-voting nodes let you replicate out to many, many nodes w/o much performance issues.
- otoolep 5y ago
  Cheers, glad you like it -- great to hear.
PeterCorless 5y ago
And likewise, Dqlite for the C folks in the crowd: https://dqlite.io/ https://dqlite.io/ [Edit] The only thing that'd be different for Rust and/or C is the avoidance of "stop-the-world" GC pauses, which affect Java more, but are still present in Golang.
- pstuart 5y ago
  dqlite has 2 other advantages over rqlite: it supports transactions, and more importantly (IMHO), it works with Go's native sql.DB handler.
  - otoolep 5y ago
    Yeah, I need to get around to creating a Go sql.DB layer. Been too busy adding to the database itself. :-) Soon!
    - pstuart 5y ago
      Please do! That was the deal breaker when I was trying to migrate an internal project to SQLite/rqlite (couldn't slap an ORM on it).
stavros 5y ago
Have you used this? Is it good? Having a distributed database seems like a great thing, but it kind of rubs me the wrong way that that database is SQLite; I associate it more with lightweight/in-process stuff, which is the opposite of distributed.
- otoolep 5y ago
  Sure, but rqlite tries to give you the best of both worlds -- a distributed database that is also lightweight and super-easy to run.
dekimir 5y ago
rqlite is not embeddable, making it harder to colocate data with computation. This post explains it: https://glaubercosta-11125.medium.com/728187331f53 https://glaubercosta-11125.medium.com/728187331f53
otoolep 5y ago
rqlite author here, happy to answer any questions about it. It seems some folks have questions about its design, and the design of systems that combine SQLite and Raft in general. Checking out the rqlite design docs might be helpful: https://github.com/rqlite/rqlite/blob/master/DOC/DESIGN.md https://github.com/rqlite/rqlite/blob/master/DOC/DESIGN.md

I came here to mention rqlite too. It's awesome, and non-voting nodes let you replicate out to many, many nodes w/o much performance issues.

otoolep 5y ago
Cheers, glad you like it -- great to hear.

PeterCorless 5y ago

And likewise, Dqlite for the C folks in the crowd: https://dqlite.io/ https://dqlite.io/ [Edit] The only thing that'd be different for Rust and/or C is the avoidance of "stop-the-world" GC pauses, which affect Java more, but are still present in Golang.

pstuart 5y ago
dqlite has 2 other advantages over rqlite: it supports transactions, and more importantly (IMHO), it works with Go's native sql.DB handler.
- otoolep 5y ago
  Yeah, I need to get around to creating a Go sql.DB layer. Been too busy adding to the database itself. :-) Soon!
  - pstuart 5y ago
    Please do! That was the deal breaker when I was trying to migrate an internal project to SQLite/rqlite (couldn't slap an ORM on it).

stavros 5y ago

Have you used this? Is it good? Having a distributed database seems like a great thing, but it kind of rubs me the wrong way that that database is SQLite; I associate it more with lightweight/in-process stuff, which is the opposite of distributed.

otoolep 5y ago
Sure, but rqlite tries to give you the best of both worlds -- a distributed database that is also lightweight and super-easy to run.

dekimir 5y ago

rqlite is not embeddable, making it harder to colocate data with computation. This post explains it: https://glaubercosta-11125.medium.com/728187331f53 https://glaubercosta-11125.medium.com/728187331f53

otoolep 5y ago

rqlite author here, happy to answer any questions about it. It seems some folks have questions about its design, and the design of systems that combine SQLite and Raft in general. Checking out the rqlite design docs might be helpful: https://github.com/rqlite/rqlite/blob/master/DOC/DESIGN.md https://github.com/rqlite/rqlite/blob/master/DOC/DESIGN.md