Re: PostgreSQL vs Mongo

One of the strengths/weaknesses of Mongo are with the similarity between
code and access. This simplifies development from a developer's
perspective, but complicates from an administrator perspective. If you want
an informed opinion, ask the same question on the Mongo mailing list. Also
look into for example Apache Cassandra.

HTH

Kind regards/met vriendelijke groet,

Serge Fonville

http://www.sergefonville.nl

2013/10/17 Bill Moran <wmoran(at)potentialtech(dot)com>

>
> If they pull out the "Mongo is faster than PostgreSQL" card, I'll state
> that
> I investigated this for my current employer and with roughly equivalent
> configurations (because it's impossible to get exactly equivalent) I was
> getting roughly the same performance from each. It's difficult to measure
> exactly, but I would recommend that if performance is a reason pulling you
> toward Mongo, that you don't listen to the internet hype and actually test
> both systems with your workload before assuming one will be faster than the
> other.
>
> On Wed, 16 Oct 2013 20:11:43 -0700 Chris Travers <chris(dot)travers(at)gmail(dot)com>
> wrote:
>
> > On Wed, Oct 16, 2013 at 8:30 AM, CS DBA <cs_dba(at)consistentstate(dot)com>
> wrote:
> >
> > > All;
> > >
> > > One of our clients is talking about moving to Mongo for their
> > > reporting/data mart. I suspect the real issue is the architecture of
> their
> > > data mart schema, however I don't want to start pushing back if I can't
> > > back it up.
> > >
> >
> > You want to find out what the issues are before making your pitch. Get
> > specifics.
> >
> > >
> > > Anyone have any thoughts on why we would / would not use Mongo for a
> > > reporting environment.
> > >
> > > what are the use cases where mongo is a good fit?
> > >
> >
> > The argument for NoSQL in reporting is where the variety of data makes
> > traditional reporting difficult. This is a niche case, and not a typical
> > data mart.
> >
> >
> > > what are the drawbacks long term?
> > >
> >
> > If you use the wrong tool for the job. you are going to find yourself
> coded
> > into corners. The tradeoff is that if you allow data variety on the way
> > in, you can't ensure simple mathematical transformation of that data to
> be
> > meaningful on the way out. This means that the precision of your answers
> > goes down once you eliminate schemas. Where you don't have to, you
> should
> > not go with a NoSQL solution for reporting.
> >
> > After all, reporting really is the forte of SQL and has been for a long
> > time.
> >
> >
> > > is mongo a persistent db or simply a big memory cache?
> > > does mongo have advantages over Postgres hstore?
> > >
> >
> > I assume Mongo docs can be nested JSON? Also you have some intraquery
> > parallelism at least between nodes. The latter can be solved with
> careful
> > use of Postgres-XC. The former would make XML on PostgreSQL a better
> > comparison.
> >
> > In general these things need to be details-oriented. It is critically
> > important to find out if they are considering it due to hype or whether
> > they have real reasons for the comparison. Maybe in some cases, NoSQL
> > options may be better, but these are relatively rare, particularly in
> > analytic environments.
> >
> > --
> > Best Wishes,
> > Chris Travers
> >
> > Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
> > lock-in.
> > http://www.efficito.com/learn_more.shtml
>
>
> --
> Bill Moran <wmoran(at)potentialtech(dot)com>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>