Edit Question - KnowledgeHub

Title Body

I am currently looking into converting a single-tenant Java based web-app that uses Spring, GWT, Hibernate, Jackrabbit, Hibernate Search / Lucene (among others) into a fully fledged SaaS style app. I stumbled across an article that highlights the following 7 "things" as important changes to make to a single tenant app to make it an SaaS app: The application must support multi-tenancy. The application must have some level of self-service sign-up. There must be a subscription/billing mechanism in place. The application must be able to scale efficiently. There must be functions in place to monitor, configure, and manage the application and tenants. There must be a mechanism in place to support unique user identification and authentication. There must be a mechanism in place to support some level of customization for each tenant. My question is has anyone implemented any of the above 7 things in a SaaS /multi-tenant app using similar technologies to those that I have listed? I am keen to get as much input regarding the best ways to do so before I go down the path that I am currently considering. As a start I am quite sure that I have a good handle on how to handle multiple tenants at a model level. I am thinking of adding a tenant ID to all of our tables and then using a Hibernate filter (and a Full Text Filter for Hibernate Search) to filter based on the logged on user's tenant ID for all queries. I do however have some concerns around performance as well especially when our number of tenants grows quite high. Any suggestions on how to implement such a solution will be greatly appreciated (and I apologise if this question is a bit too open-ended).

Tags (comma-separated) Cancel