| From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Using Postgresql as application server |
| Date: | 2011-08-16 05:52:20 |
| Message-ID: | CAKt_ZftbUeUPycofs1dqRbTvvqowi5_wA-7H1mdCa+kM_412tg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Mon, Aug 15, 2011 at 10:05 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>
> 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.
>
The other big scalability limitation for Pg as an app server is you
really can't do connection pooling.
Best Wishes,
Chris Travers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sad@bestmx.ru | 2011-08-16 07:45:59 | Re: Using Postgresql as application server |
| Previous Message | Scott Marlowe | 2011-08-16 05:05:13 | Re: Using Postgresql as application server |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abbas | 2011-08-16 06:26:27 | Re: idle in transaction process |
| Previous Message | Scott Marlowe | 2011-08-16 05:05:13 | Re: Using Postgresql as application server |