Not sure if this was mentioned, but MongoDB is strongly consistent while
Cassandra is eventually consistent -- at least about a month ago when I
looked at it in more detail, though with vector clocks in 0.7, this may be
less of an issue.
Did Mongo switch away from the fsync() every now and
Thanks for pointing this out. My fault in thinking Mongo is another
java-based database, which I will probably realize wrong when I attend the
mongo conference in a week.
On Fri, May 14, 2010 at 4:45 AM, David Strauss da...@fourkitchens.comwrote:
On 2010-05-13 19:48, Steve Lihn wrote:
Now the
In a perfect world there should be (aiming for) a new major Cassandra release
every 2-3 months.
// Roger Schildmeijer
On 13 maj 2010, at 19.43em, Sandeep Kalidindi wrote:
Any idea about how far the 0.7 release is ??
Cheers,
Deepu.
On Thu, May 13, 2010 at 10:52 PM, Vijay
What is changing? A more flexible schema or no need to restart (some kind of
hot-reboot)?
Mongo guys claims that Mongo's advantage is a schema-less design. Basically
you can have any data structure you want and you can change them anyway you
want. This is done in the name of flexibility, but I am
Cassandra has always enforced the tiniest bit of schema. You
basically define how you want your columns and subcolumns to be sorted
within column families. You also name the column families and
keyspaces. That's all though.
The part that is changing is that the keyspaces and column families
Mongo has a rich query API and a weak distribution/replication story.
Cassandra has a narrow (read: weak) query API and a strong
distribution/replication story. If you want really shallow learning
curve, easy querying, etc, won't have that much data, and are handy
with the typical master/slave
MongoDB encourages you to define your schema in your application code by
using mapping classes. This logically infers that it makes no sense to
define the schema twice, in the database and in your application code.
On Fri, May 14, 2010 at 3:48 AM, Steve Lihn stevel...@gmail.com wrote:
What is
Not sure how to comment on this concept. I guess it infers that the database
and application are no longer loosely coupled, but now strongly coupled.
I guess too, that java developers will vote yes, while database architect
and DBA will vote no.
In the traditional sense, enterprise data is the
You can choose to have keys ordered by using an
OrderPreservingPartioner with the trade-off that key ranges can get
denser on certain nodes than others.
On Wed, May 12, 2010 at 7:48 PM, philip andrew philip14...@gmail.com wrote:
Hi,
From my understanding, Cassandra entities are indexed on only
