| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andrej <andrej(dot)groups(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, c k <shreeseva(dot)learning(at)gmail(dot)com>, Chris Travers <chris(dot)travers(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, sad(at)bestmx(dot)ru |
| Subject: | Re: Using Postgresql as application server |
| Date: | 2011-08-28 17:09:41 |
| Message-ID: | m2zkit5up6.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
[edited]
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>>>> http://asmith.id.au/mod_libpq.html
>> http://asmith.id.au/source/mod_libpq2.c
>
> node.js is even thinner.
>
> node.js is single threaded and 100% asynchronous which fits very nice
> with libpq which is at heart a single threaded asynchronous library.
Sure. Elnode shares this design, and yaws more seriously so. I
wouldn't pick mod_libpq myself.
http://nic.ferrier.me.uk/blog/2010_10/elnode
http://yaws.hyber.org/
Just saying that the thin web server layer that directly hands the
request to the database has been existing in PostgreSQL land for a long
time already, no need to resort to other proprietary architectures here.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adarsh Sharma | 2011-08-29 04:48:14 | Get data back after drop Command |
| Previous Message | Merlin Moncure | 2011-08-28 15:13:52 | Re: Using Postgresql as application server |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2011-08-28 17:49:27 | Re: Problem importing a csv file |
| Previous Message | Ian Pilcher | 2011-08-28 16:23:56 | Re: JDBC Connection Errors |