Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 8E093B5DBCC for ; Mon, 15 Aug 2011 11:50:38 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 98592-04 for ; Mon, 15 Aug 2011 14:50:32 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from prod2.officenet.no (www.officenet.no [195.159.87.248]) by mail.postgresql.org (Postfix) with ESMTP id EF83BB5D803 for ; Mon, 15 Aug 2011 11:50:31 -0300 (ADT) Received: from localhost ([127.0.0.1] helo=prod2) by prod2.officenet.no with esmtp (Exim 4.71) (envelope-from ) id 1QsyUn-0005JL-Eb; Mon, 15 Aug 2011 16:50:29 +0200 Date: Mon, 15 Aug 2011 16:50:28 +0200 (CEST) From: Andreas Joseph Krogh To: Merlin Moncure , pgsql-general@postgresql.org Message-ID: <28771520.11.1313419828780.JavaMail.on@prod2> In-Reply-To: Subject: Re: Using Postgresql as application server MIME-Version: 1.0 User-Agent: Origo 1.9.0-SNAPSHOT X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.971 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-1.071 X-Spam-Level: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archive-Number: 201108/436 X-Sequence-Number: 178718 P=C3=A5 mandag 15. august 2011 kl 16:36:23 skrev du: > On Sat, Aug 13, 2011 at 2:30 PM, Andreas Joseph Krogh > wrote: > > No, PG has never, and will never, act as an application-server. >=20 > Why in the world not? Now, it may or may not be a good idea but there > is no technical constraint that prevents postgresql from being used in > this fashion. I think it's a fine idea. >=20 > Postgresql has certain features, in particular being able to implement > functions in any language, that make it uniquely well suited among its > peers to act as a application server platform. Having a > quasi-functional front end to your middeware procedural code is very > powerful as is having direct access to a local data store for caching > and spooling purposes. So powerful that I would argue that if > properly supported by tools it would be superior to many of the more > classic stacks in use today. I could go down the list of reasons why > that's the case -- tight coupling with data, performance, emphasis on > transactional coding, etc. There are downsides too, but those could > be mitigated with some thought and work. >=20 > Postgres is not just a database -- it's a language hosting platform if > you want to use it as such. Now, you can continue to do things as > you've always done (database 'here', code 'here', web server 'here'), > but why discourage people from trying out different things? >=20 > merlin Sorry if I stepped on any toes here. But seriously - by my definition of ap= p-server PG is not suited at all. I strongly would discourage anyone from u= sing any RDBMS as an app-server. *IMO* it makes development, testing, separ= ation-of-consern, debugging and re-deployment a nightmare. PG has a lot of nice DB-features and I use it every day, but as an app-serv= er - no way. -- Andreas Joseph Krogh Senior Software Developer / CTO Public key: http://home.officenet.no/~andreak/public_key.asc ------------------------+---------------------------------------------+ OfficeNet AS | The most difficult thing in the world is to | Rosenholmveien 25 | know how to do a thing and to watch | 1414 Troll=C3=A5sen | somebody else doing it wrong, without | NORWAY | comment. | Org.nr: NO 981 479 076 | | | | Tlf: +47 24 15 38 90 | | Fax: +47 24 15 38 91 | | Mobile: +47 909 56 963 | | ------------------------+---------------------------------------------+