[Flow] How to build a SaaS Service?

[Dominique Feyer]

We have a SaaS Flow application, with single database and one subdomain per
client. Client can choose an custom domain name, if needed (in this case
Flow build the Nginx proxy configuration to do the mapping on the Nginx
level.

Single database is a bit more complexe (security wise, but with some nice
aspect you can separate each domain nicely), but dealing the Private and
Shared models if more easy in a single database than with a multi database
setup. I our case this was a requirement.

With multi database, you need to take care of multiple database migration,
... so pushing thing in production can be more complex (how to rollback if
only one database failed, but all the others succeed, ...).

For the performance perspective, I think that's not a real problem. MySQL
and Postgres perform well with huge amout of data. And the difference
between multiple small database and a big single one ... can make no
difference.

On thing that can be easier with multi database, is backup and restore of
user data. In our case, we have a custom import/export to XML to handle
this case.

Bests,

Dominique Feyer

ttree sarl
Dominique Feyer
TYPO3 Addict
Rue du Valentin 34 et demi
CH - 1004 Lausanne
Téléphone +41 21 312 36 35
www.ttree.ch | twitter <http://twitter.com/ttreeagency> |
linkedin<http://www.linkedin.com/company/ttree/>
Plan d'accès: http://g.co/maps/4yu6t


2014-02-24 11:40 GMT+01:00 Axel Wüstemann <awu at qbus.de>:

> My idea to use a database per account is to separate the accounts
> compeletey (regarding to privacy and security) and to have smaller
> databases (regarding performance)
>
> But maybe that are not good ideas?
>
> Thank you
> Axel
>
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>