Re: PostgreSQL vs Mongo

From: Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org>, cs_dba(at)consistentstate(dot)com
Subject: Re: PostgreSQL vs Mongo
Date: 2013-10-16 20:56:46
Message-ID: CAM6mieLW7H1TAmv1A6yRvxXHVD9=U4i4ZNo51hCxsOrH2HOPFg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On 17 October 2013 02:30, CS DBA <cs_dba(at)consistentstate(dot)com> wrote:
> Anyone have any thoughts on why we would / would not use Mongo for a
> reporting environment.

hm.. I wouldn't use anything which doesn't support rich SQL as a
backed for reporting system. In mongo, simple selects are fine but
anything complex requires map-reduce style query. Hence you need real
developers to maintain it.

> what are the use cases where mongo is a good fit?
> what are the drawbacks long term?
> is mongo a persistent db or simply a big memory cache?
> does mongo have advantages over Postgres hstore?

This is very good summary: http://aphyr.com/posts/284-call-me-maybe-mongodb
(entire "Call me maybe" series is good: http://aphyr.com/tags/jepsen,
even Postgres is there)

The problem with all NoSQL solutions is that they are selected based
on the features and APIs not based on consistency vs. availability
tradeoffs. Moreover, distributed system should have partition
tolerance and many NoSQL dbs simply drop data in this case.

--
Ondrej

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Moshe Jacobson 2013-10-16 20:57:15 Bug? Function with side effects not evaluated in CTE
Previous Message Bruce Momjian 2013-10-16 20:53:16 Re: Major upgrade of PostgreSQL and MySQL