When to add multi tenancy ?

[Leandro França]

Hi there,

I'm building a new app that will need to have multi tenancy features and I'd like to hear some opinions.

When do you guys think is a good time to add multi tenancy feature? 
Do you usually add it from the ground up or just at a later stage?

Thanks,
Leandro

[Chris Lerum]

You seem to answer your own question: you already know it's an architectural requirement, so I'd suggest including it from the beginning.

[Thiago Cifani]

If it will have some multitenancy requirements, I think your app will have to be born with it. The perfect time is always in the beginning, green field coming.

Enviado do meu iPhone

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/c5d3a318-2159-4977-8b84-09fe6c450337%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Leandro França]

Thanks for replying.

I'm now deciding on the best approach to take.

I was all set up to use act_as_tenant and devise.

But after reading some of Ryans posts (https://leanpub.com/multi-tenancy-rails) , I'm not sure this is the best way.

Any insights on tried and true real world implementations of multi tenancy? 
PS.: I'm looking around for something scope based