Hi Matteo
We're not even close to the 200+ customers you're planning to have.
But we've got 25 sites running in one author and one public instance.
I don't see the point in having an author instance for each
customer... but having a public instance per customer would be fine.
Or even better: extend the functionality of the cache module so that
activating content does not clear the whole cache but only a part, e.g.:
When activating anything underneath /siteA/... only clear the cache
for /siteA/... and /docroot/siteA/...
This would pretty much boil down to having a cache which is
configurable with custom rules. Otherwise you can turn of the cache in
the first place. Because with 200+ customers you'll constantly have
someone activating content and therefore clearing out the whole cache.
-will
On 08.06.2009, at 09:27, Matteo Pelucco wrote:
Hi all,
we are going to use Magnolia as CMS on our SAAS Platform.
We have still some doubts about some topics:
1) Having to serve about 200+ (little) customer, we are wondering
which is the best between:
-A- Have one Magnolia Author for each customer
-B- Share the same Magnolia instance between different customers
In "A" case, how many public instances, assuming each website has
the same traffic?
In "B" case, how many customers on the same Magnolia Instance?
2) Freemarker or JSP?
In a SAAS environment we think Freemarker is a good choice, because
it avoid FTP access for JSP templates, JAR packeting, deep Java
knowledge... and we have versioning over templating. Any other
suggestion on it?
Can you share your ideas on this topic? I would be glad..
Thanks in advance!
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
