How are SaaS applications organized?
Posted
by tomekw
on Stack Overflow
See other posts from Stack Overflow
or by tomekw
Published on 2010-04-27T07:25:30Z
Indexed on
2010/04/27
9:03 UTC
Read the original article
Hit count: 357
Consider web (MVC, for example Rails) application for multiple clients as a service.
How to design this?
one application instance per client? (+ one database per client)
one instance for all clients (+ one database for all clients)
Former one is simple, but... "inefficient". How about the latter? (best practises, design patterns) How to separate client data? For example: worker "A" of client "1" has two documents, worker "B" of client "2" has three documents. How to build model associations to protect other users (and clients) data? I think joining every query with Client model is not a good solution.
© Stack Overflow or respective owner