| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Andreas Joseph Krogh <andreak(at)officenet(dot)no>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Using Postgresql as application server |
| Date: | 2011-08-16 05:05:13 |
| Message-ID: | CAOR=d=0XN6Wrueh8rhE=X+Jb-MMPhy2kbfteMmprxMiNvuCLPg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Mon, Aug 15, 2011 at 7:23 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> There are downsides too -- you lose access to the excellent middleware
> tools out there, and you are 'stuck' on postgres and need to come up
> with hard to find and expensive postgres talent. You need to be
> prepared to blaze a path, etc etc.
Yep. Also, it's REAL easy to stick a caching layer like memcached
into the middle tier app layer, but nearly impossible to do so in
pgsql. For large systems, this would make pg as an app server a nogo.
But for small to medium sized systems that don't need caching it
could work out.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2011-08-16 05:52:20 | Re: Using Postgresql as application server |
| Previous Message | Venkat Balaji | 2011-08-16 05:05:11 | Re: Postgresql 9.0.1 installation error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2011-08-16 05:52:20 | Re: Using Postgresql as application server |
| Previous Message | Fujii Masao | 2011-08-16 04:34:28 | Re: streaming replication: one problem & several questions |