From: Chris Travers <chris@travelamericas.com>
To: Marcos <mjs_ops@gmx.net>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Decide between Postgresql and Mysql (help of
Date: Tue, 28 Mar 2006 12:50:53 -0800
Message-ID: <4429A1AD.4030104@travelamericas.com> (raw)
In-Reply-To: <1143564928.1241.28.camel@servidor>
References: <1143559902.1241.16.camel@servidor>
<1143572392.3625.79.camel@state.g2switchworks.com>
<1143564928.1241.28.camel@servidor>
Marcos wrote:
>>So, what exactly are you planning on doing?
>>
>>
>
>The application will be a chat for web, the chats will be stored in the
>server. In a determined interval of time... more or less 2 seconds, the
>application will be looking for new messages.
>
>I believe that it will make many accesses. The write in disc will be
>constant.
>
>
Ok. I would favor PostgreSQL for reasons of ease of future
development. However, lets look at what both RDBMS's buy you:
MySQL:
1) Possibility of many components for web apps that can be used though
the lack of certain features (such as complex updateable views) makes
this possibly an issue.
2) Great simple read performance.
PostgreSQL:
1) Possibility to integrate any other components later (including those
on MySQL via DBI-Link).
2) Fabulous community support (and I am sure fabulous paid support too
given the fact that many of those who contribute to the great community
support also offer paid support).
3) Better parallel write performance.
4) Greater extensibility, leading to greater flexibility down the road
should you want to add in new components without rewriting your front-end.
For a simple chat client, you can probably put something together with
some Perl/CGI scripts, Jabber, and MySQL or PostgreSQL pretty easily and
without much development labor at all. Indeed I would suggest that the
RDBMS is, absent other specific concerns, the least of your issues.
In other words, both are probably adequate. It is impossible to provide
an estimate for capacity though without knowing the app in question,
expected query composition, and so forth.
Best Wishes,
Chris Travers
Metatron Technology Consulting
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: chris@travelamericas.com, mjs_ops@gmx.net, smarlowe@g2switchworks.com
Subject: Re: Decide between Postgresql and Mysql (help of
In-Reply-To: <4429A1AD.4030104@travelamericas.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox