Yes, I did read through his points. Did you read my response, basically saying that a SaaS application is not much different from any other typical Rails application? Indeed, that is true, as I've experienced time and time again in building and deploying my own SaaS applications, and in seeing others deploy theirs.
The one point that he did ask about that is specific to SaaS applications is the database design behind multi-tenant applications, and this is the point that I chose to address. Again, it is true, that it is a simple matter of using Rails' association scoping to achieve the desired result of having all customer data in one database but easily restricting the queries so as not to allow one customer to view another customer's data. Futher, I mention the SaaS Rails Kit because it is relevant to the question. This product demonstrates rather clearly how to use Rails' association scoping to achieve that outcome. While the SaaS Rails Kit does provide a billing system, it is not just a billing system, but an example of framework of how to build the type of application that was the subject of the original author's inquiry. -- Benjamin Curtis http://railskits.com/ - Ready-made Rails code http://catchthebest.com/ - Team-powered recruiting http://www.bencurtis.com/ - Personal blog On Fri, Sep 26, 2008 at 2:01 PM, Victor Al <[EMAIL PROTECTED] > wrote: > > Benjamin, > > Not only do I think that what you are doing is indeed "shameless self > promotion", but I think that you are seriously misunderstanding the > concept of SaaS and promoting bad information about RoR and SaaS on the > web. > > Did you read through the points John asked about above? > > He is asking about: > -Scalability > -Multi-tenant database design > -Configurability > -Security > > These points are expressed in more detail in the article at > http://msdn.microsoft.com/en-us/library/aa479069.aspx > but unfortunately there is little RoR specific information about them on > the web. > > From what you write on your website, the only thing you are providing is > a billing system. Labeling that as "SaaS" is misleading in the extreme. > > Victor > > > Benjamin Curtis wrote: > > This is, of course, shameless self promotion, but the SaaS Rails Kit > > that I > > created could definitely point you in the right direction with some > > working > > code: http://railskits.com/saas/ (n.b., it's not free). > > > > To generally answer your questions, though, it's not that different from > > your typical Rails app. You can use a single database with appropriate > > query scoping to restrict tenants to only seeing their data. > > > > -- > > Benjamin Curtis > > http://railskits.com/ - Ready-made Rails code > > http://catchthebest.com/ - Team-powered recruiting > > http://www.bencurtis.com/ - Personal blog > > > > > > > > > > > > On Tue, Sep 16, 2008 at 9:50 AM, John John > > <[EMAIL PROTECTED] > > -- > Posted via http://www.ruby-forum.com/. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
