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

From Frank Lanitz
Subject Re: Implementing "thick"/"fat" databases
Date
Msg-id 4E2D2420.8060900@frank.uvena.de
Whole thread Raw
In response to Implementing "thick"/"fat" databases  ("Karl Nack" <karlnack@futurityinc.com>)
Responses Re: Implementing "thick"/"fat" databases  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: Implementing "thick"/"fat" databases  (Sim Zacks <sim@compulab.co.il>)
List pgsql-general
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.

Cheers,
Frank

pgsql-general by date:

Previous
From: Simon Riggs
Date:
Subject: Re: streaming replication does not work across datacenter with 20ms latency?
Next
From: Pavel Stehule
Date:
Subject: Re: Implementing "thick"/"fat" databases