4 ms·
None of these can be definitively affirmed or rejected by facts. They're interesting questions but they're either unanswerable (time, oodb) or entirely applica
by skorgu 17y ago
None of these can be definitively affirmed or rejected by facts.
They're interesting questions but they're either unanswerable (time, oodb) or entirely application dependent (pain, hiring).
- justinsb 17y agoPerhaps not, but this doesn't make them unimportant, and again this is why it's clever marketing. Frame the discussion in terms of things that you do well, even if they're not the most important considerations (e.g. "one keyspace per install"). It's a good sales technique: "Do you like holidays?" "Yes" "Well, now that I know you can say yes, do you want to buy this product?"
- Semiapies 17y agoNor are they "objections".
- justinsb 17y agoThey're certainly fairly big reasons not to use Cassandra, and as such I'd put them in the objections bucket. If you're objecting to the fact that I phrased them as questions, just pretend we're on Jeopardy :-)
- jbooth 17y agoNo they're not, a "big reason not to use Cassandra" would be "it has critical bug X" or "it's missing critical feature Y".