4 ms·

So, mysql is a frontend to InnoDB? Cockroach is a frontend to RocksDB? Note: Redix has a pluggable storage engine, the current engine is "badgerdb", the next i

So, mysql is a frontend to InnoDB? Cockroach is a frontend to RocksDB? Note: Redix has a pluggable storage engine, the current engine is "badgerdb", the next is "bolt" and it is already integrated and I'll release it soon.

cperciva 8y ago
So, mysql is a frontend to InnoDB? I would put it the other way around: InnoDB is a backend for MySQL. But an SQL database is far more complicated than a key-value store, and has a lot of "middle end" between the "talk to the client" front end and the "store stuff on disk" back end. I'm not saying that RedixDB isn't interesting -- having a network front-end to Badger seems like it would extremely useful for most people who want to use Badger. It's just that I spent a while digging through the code trying to figure out where the back end was and what data structures you were using, only to discover that you didn't have a backend (or rather, you're using a pre-existing one).
- throwaway12iii 8y ago
  Your second comment is less friendly than your first. Maybe just stop.
- kieckerjan 8y ago
  Second that. It would help if you included on the website some info about the technical implementation. That would help instill confidence in the solution.
networkimprov 8y ago
None of these backends currently fsync() correctly on MacOS, due to a Go bug fixed in 1.12.
- fulafel 8y ago
  To split hairs, the bug is in MacOS - its fsync() does not flush data to stable storage. Go 1.12 includes a workaround for this MacOS bug.
  - networkimprov 8y ago
    To split further, it's a MacOS design flaw, with a published workaround. It is a bug to fail to use the workaround :-)
    - fulafel 8y ago
      I don't know if Apoke really acknowledges it as a bug or flaw. Their man page for fsync reads like an intentional misunderstanding of fsync semantics.
rlaanemets 8y ago
There is also Facebook's MyRocks which is MySQL frontend with RocksDB backend. It has lower write amplification than InnoDB, which is the main reason why it was created.

cperciva 8y ago

So, mysql is a frontend to InnoDB? I would put it the other way around: InnoDB is a backend for MySQL. But an SQL database is far more complicated than a key-value store, and has a lot of "middle end" between the "talk to the client" front end and the "store stuff on disk" back end. I'm not saying that RedixDB isn't interesting -- having a network front-end to Badger seems like it would extremely useful for most people who want to use Badger. It's just that I spent a while digging through the code trying to figure out where the back end was and what data structures you were using, only to discover that you didn't have a backend (or rather, you're using a pre-existing one).

throwaway12iii 8y ago
Your second comment is less friendly than your first. Maybe just stop.
kieckerjan 8y ago
Second that. It would help if you included on the website some info about the technical implementation. That would help instill confidence in the solution.

networkimprov 8y ago

None of these backends currently fsync() correctly on MacOS, due to a Go bug fixed in 1.12.

fulafel 8y ago
To split hairs, the bug is in MacOS - its fsync() does not flush data to stable storage. Go 1.12 includes a workaround for this MacOS bug.
- networkimprov 8y ago
  To split further, it's a MacOS design flaw, with a published workaround. It is a bug to fail to use the workaround :-)
  - fulafel 8y ago
    I don't know if Apoke really acknowledges it as a bug or flaw. Their man page for fsync reads like an intentional misunderstanding of fsync semantics.

rlaanemets 8y ago

There is also Facebook's MyRocks which is MySQL frontend with RocksDB backend. It has lower write amplification than InnoDB, which is the main reason why it was created.