# Drb / ActiveRecord as Application Server for Qt/Ruby client **URL:** \ **Category:** Ruby\ **Created:** [August 4, 2006, 9:26am UTC](https://www.ruby-forum.com/t/drb-activerecord-as-application-server-for-qt-ruby-client/101327 "2006-08-04T09:26:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![philpraxis](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/77aa72/32.png) [@philpraxis](https://www.ruby-forum.com/u/philpraxis)\ **Post date:** [August 4, 2006, 9:26am UTC](https://www.ruby-forum.com/t/drb-activerecord-as-application-server-for-qt-ruby-client/101327/1 "2006-08-04T09:26:07Z")
Hi, I intend to start a new project with the following architecture: ## Server: - Postgresql database - ActiveRecord - Distributed Ruby Server ## Client: - Distributed Ruby Client - Qt/Ruby GUI Drb is not really an “Application Server”. Normally, you expect features like “Connection Pooling” from such a server, and much more. Is it safe and robust, anyway, on an intranet composed of a hundred of client computers, to marshall all ActiveRecord objects through a simple drb server? Has anyone done this already? Your reactions are more than welcome! Thanks ---
**Author:** ![philpraxis](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/77aa72/32.png) [@philpraxis](https://www.ruby-forum.com/u/philpraxis)\ **Post date:** [August 4, 2006, 4:42pm UTC](https://www.ruby-forum.com/t/drb-activerecord-as-application-server-for-qt-ruby-client/101327/2 "2006-08-04T16:42:29Z")
On Aug 4, 2006, at 3:24 AM, Philippe L. wrote: > Client: > simple drb server? > > Has anyone done this already? > > Your reactions are more than welcome! > > Thanks If you are just gonna marshal the AR objects and send them across the network, why even have a server / client architecture? Just stick the AR code in the “Client” and let PostgreSQL worry about concurrency.