3 ms·
If you release something new, you should make sure that your documentation contains useful information. Even the most fundamental information like available co
by aeyes 4y ago
If you release something new, you should make sure that your documentation contains useful information.
Even the most fundamental information like available configuration options, command-line arguments, deployment information and so on is missing.
Looking at the code it appears that you need Consul, Zookeeper and Redis to make this fly and the docs don't mention this anywhere. They (barely) explain how to run the SQL proxy on a local machine but thats it.
I wonder if the testimonials on your website are just pulled from thin air, I don't think any sane person would even experiment with this anywhere near production environments.
- deleted 4y ago[deleted]
- greg-m 4y agoHey, PM @ ReadySet - fair points, and thanks for checking us out. We've been in pretty heavy development and have been heads down on getting ReadySet into your hands as quickly as we could. We'll be doing a major documentation pass soon which will have more info about clustering, etc. There's also a bit more detail in our development guide - see https://github.com/readysettech/readyset/blob/main/development.md https://github.com/readysettech/readyset/blob/main/developme...
- latchkey 4y agoFrom the blog post "Rather than forcing developers to switch to a key-value store"... > need Consul, Zookeeper and Redis to make this fly A hard dependency on 3 key value stores?
- marzoeva 4y agoWe need either Consul or Zookeeper (for leader election). No dependency on Redis! That part of the blog post refers to ReadySet having a SQL interface, rather than a key-value one.
- cpursley 4y agoElixir/Erlang is not the most memory efficient, but it could be used for something like this without the need for Redis for Consul/Zookeeper.
- deleted 4y ago[deleted]