4 ms·
I really don't like how you keep sidestepping the hard questions that were raised. Instead of curling up in semantics discussions, how about simply answering a
by moe 17y ago
I really don't like how you keep sidestepping the hard questions that were raised.
Instead of curling up in semantics discussions, how about simply answering a few of those? I think you could do that without revealing anything about the magic sauce of your product.
To reiterate:
* Does your system support the full SQL vocabulary, including all join types?
* Is it ACID?
* Do I really not have to arrange my data in any special way (schema-, or partition-wise)?
* Does it really scale near-linear, regardless of the workload that I apply?
* Why do you bother with MySQL-Hosting as a secondary product if your new db scales down just fine?
- justinsb 17y agoIt might seem to you that we can answer these questions without revealing secrets, but consider that (1) I've not been answering them and (2) you're asking whether we can do what was thought to be impossible, so real answers will necessarily provide direction. Short answers will just annoy you, full answers will reveal too much, and frankly, there's little upside in replying. If you'd make a good early-adopter customer for us, contact us and we can have the discussion. But equally, I see that you haven't replied to my call for early-adopters! One I can definitely answer: yes, full SQL vocabulary support (though we haven't implemented everything yet!)
- moe 17y agoShort answers will just annoy you, full answers will reveal too much Oh well, a simple yes or no would be fine, really. However, I guess it's safe to assume then, that you're not ACID and that data will have to be rearranged to accomodate your system. That's my take-home because a simple "yes" to either question would not have revealed anything.
- justinsb 17y agoWell, if you promise it won't annoy you: Yes, Yes, Correct, Yes (for non-pathological workloads), Choice is good