Re: Implementing "thick"/"fat" databases - Mailing list pgsql-general

From Pavel Stehule
Subject Re: Implementing "thick"/"fat" databases
Date
Msg-id CAFj8pRBuCAA2JHYkH3pfT2kYOn_fuT9jFYbqh=FE2+RWSwWWGQ@mail.gmail.com
Whole thread Raw
In response to Re: Implementing "thick"/"fat" databases  (Frank Lanitz <frank@frank.uvena.de>)
Responses Re: Implementing "thick"/"fat" databases  (Frank Lanitz <frank@frank.uvena.de>)
List pgsql-general
2011/7/25 Frank Lanitz <frank@frank.uvena.de>:
> Am 22.07.2011 21:15, schrieb Karl Nack:
>>
>> to move as much business/transactional logic as
>> possible into the database, so that client applications become little
>> more than moving data into and out of the database using a well-defined
>> API, most commonly (but not necessarily) through the use of stored
>> procedures.
>
> Beside the points already mentioned, doing this will might cause bottle
> necks if you have complicated transactions as the DB-cluster might can not
> be scaled as good as maybe a farm of application server could be done.
>

Yes, and no - this can decrease network overhead, can decrease a data
conversion overhead. Sometimes I was surprised how much time I got
with moving to stored procedures.

Regards

Pavel

> Cheers,
> Frank
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

pgsql-general by date:

Previous
From: Frank Lanitz
Date:
Subject: Re: Implementing "thick"/"fat" databases
Next
From: "Markus Wollny"
Date:
Subject: Query, usually running <300ms, sometimes hangs for hours