| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Evan Rempel <erempel(at)uvic(dot)ca>, "sad(at)bestmx(dot)ru" <sad(at)bestmx(dot)ru>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Using Postgresql as application server |
| Date: | 2011-08-16 18:32:07 |
| Message-ID: | CAOR=d=0MzGO4Jat7q3V_=JC=4+RQNotxFFN0zo4NtA6E_Ykyjw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Tue, Aug 16, 2011 at 12:25 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> one point that is getting lost in all this that if you are using a
> database for an application server, this does not mean it's the same
> database as your main database or even on the same machine -- you can
> still keep traditional separation of roles and use something like
> dblink to transfer data. regarding the use of postgres functions for
I'm thining pl/proxy would be pretty amazing here. I still prefer
using another layer in another language for an app server, but now
that you've got me thinking a bit more out of the box, pl/proxy would
increase your ability to scale quite a lot.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | c k | 2011-08-16 18:38:37 | Re: [GENERAL] Using Postgresql as application server |
| Previous Message | Merlin Moncure | 2011-08-16 18:25:00 | Re: [GENERAL] Using Postgresql as application server |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | c k | 2011-08-16 18:38:37 | Re: [GENERAL] Using Postgresql as application server |
| Previous Message | Merlin Moncure | 2011-08-16 18:29:46 | Re: join between a table and function. |