On 8/28/05, Dewey Howell <deweyhowell@[...].com>  wrote:
>  Hello
>  
>  I am preparing a number of apps for physicians, hospitals, pharmacists
>  & other health-care providers.  I began my development using
>  php/postgresql which has been working well enough, but as my apps have
>  grown I quickly see that I need to make some changes to make them
>  maintainable, customizable and scalable.    While there are certainly
>  a number of improvements I can make with my php apps to improve my
>  coding/app design (which I am actively doing) but the idea of Rails is
>  appealing to help facilitate good code design, maintenance, testing,
>  etc.
>  
>  My question is Rails appropriate for a potentially large application
>  with eventually hundreds of concurrent users, loads and loads of data
>  coming in and out of the database, requiring robust security?  I have
>  seen the following example Rails apps.
>  
>  http://wiki.rubyonrails.com/rails/show/RealWorldUsage
>  
>  But don't have a good sense of how these would compare to a large
>  healthcare IT solution.
>  In short is Rails a good choice for my solution?  Are there
>  advantages/disadvantages that I haven't considered?
>  
>  I am trying to make good planning decisions early in my small startup
>  before I lose the ability to make changes quickly and easily.

Rails uses the same model for scaling as livejournal, flickr, etc. 
See http://www.loudthinking.com/arc/000479.html

Database security shouldn't be any different in Rails than it is with
any other language/framework.
_______________________________________________
Rails mailing list
Rails@[...].org
http://lists.rubyonrails.org/mailman/listinfo/rails