Re: Implementing "thick"/"fat" databases

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Frank Lanitz <frank(at)frank(dot)uvena(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Implementing "thick"/"fat" databases
Date: 2011-07-25 08:12:01
Message-ID: CAFj8pRBuCAA2JHYkH3pfT2kYOn_fuT9jFYbqh=FE2+RWSwWWGQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2011/7/25 Frank Lanitz <frank(at)frank(dot)uvena(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Frank Lanitz 2011-07-25 08:22:33 Re: Implementing "thick"/"fat" databases
Previous Message Frank Lanitz 2011-07-25 08:06:56 Re: Implementing "thick"/"fat" databases