Re: Implementing "thick"/"fat" databases
От | Pavel Stehule |
---|---|
Тема | Re: Implementing "thick"/"fat" databases |
Дата | |
Msg-id | CAFj8pRBuCAA2JHYkH3pfT2kYOn_fuT9jFYbqh=FE2+RWSwWWGQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Implementing "thick"/"fat" databases (Frank Lanitz <frank@frank.uvena.de>) |
Ответы |
Re: Implementing "thick"/"fat" databases
|
Список | 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 по дате отправления: