61–66 of 66 posts
Earlier quoted context omitted.
Did you have to pay Kyle for him to test your database?
Yep! Testing databases is my full time job. Vendors pay me for the work, and that means the Jepsen library, test harness for each database, and all the reports are free for everyone. :)
Can anyone share their production experience with Dgraph?
Earlier quoted context omitted.
Yep! Testing databases is my full time job. Vendors pay me for the work, and that means the Jepsen library, test harness for each database, and all the reports are free for everyone. :)
Does the Jepsen test require you to host the databases or can you test a system completely remotely?
Earlier quoted context omitted.
Does the Jepsen test require you to host the databases or can you test a system completely remotely?
Sure, I could run Jepsen against anything I can talk to over the network, but a.) it might be painful or impossible to get a fresh, healthy cluster for each test run (It's... fairly common that databases stop being databases during a test) and b.) doing fault injection means I need a way to, well, inject faults. That's why Jepsen tests almost always involve Jepsen controlling the cluster.
Earlier quoted context omitted.
Sure, I could run Jepsen against anything I can talk to over the network, but a.) it might be painful or impossible to get a fresh, healthy cluster for each test run (It's... fairly common that databases stop being databases during a test) and b.) doing fault injection means I need a way to, well, inject faults. That's why Jepsen tests almost always involve Jepsen controlling the cluster.
Ok, what are the API calls you need now, and would need to remotely inject faults? Can you make a HTTP server API with a client implementation for it so that we can just make implement the server API and point your test cluster to the nodes for automatic testing? I understand this would be counter to you making your living out of this, but think of it as a "light" pro-bono version!
Earlier quoted context omitted.
Sure, I could run Jepsen against anything I can talk to over the network, but a.) it might be painful or impossible to get a fresh, healthy cluster for each test run (It's... fairly common that databases stop being databases during a test) and b.) doing fault injection means I need a way to, well, inject faults. That's why Jepsen tests almost always involve Jepsen controlling the cluster.
Ok, what are the API calls you need now, and would need to remotely inject faults? Can you make a HTTP server API with a client implementation for it so that we can just make implement the server API and point your test cluster to the nodes for automatic testing? I understand this would be counter to you making your living out of this, but think of it as a "light" pro-bono version!