Hi fellow railers!
We are discussing the possibility of writing a very large application in
Rails. By “very large” I mean a framework that would contain a few
hundred smaller applications that would need to talk to one big database
and have to share some common session data I’d like to get some
feedback on some possible ways of doing the following:
The application would basically run the university. It would handle
accounts payable, accounts receivable, financial aid, course
registration, student advising, payroll, grade checking, grade
submission, student housing, etc.
We’re working with Yale’s CAS system and we’ve got that working fine
with Rails, so single-sign-on isn’t a problem, but we would like to be
able to share session data across all of these applications.
So our thought is that we would just make one big Rails application.
However, the following questions come up:
How would we separate those sub-programs (grade submission) into
“modules” so we could organize the models, views and controllers?
Components looks like one way, but does that make sense?
Would we be able to deploy a new “module” (grade checking for
example) without bringing down the whole system? (not a big deal, just a
We’ve currently got an idea of how to do this with
Spring+Hibernate+Sitemesh+some_other_Java_buzzwords and we’re not making
I would appreciate any comments on this. We’re just looking for
Thank you very much!
Learning & Technology Services
University of Wisconsin-Eau Claire
715 836 3585