What is MultiTenancy?
This is important because this is crucial to mass adoption of the solution in a way that is economical. More money for Lecere, higher PPS for us!
In laymen's terms: Do more with less, and keeping it secure. It's a design philosophy according to how they develop the solution. Imagine building a house on a brick foundation as opposed to using mud.
Lecere could go to market quicker without multi-tenancy, but some of the cool features we would want would be more difficult to obtain...and the solution would require more resources.
According to Wikopedia:
Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants). Multitenancy is contrasted with a multi-instance architecture where separate software instances (or hardware systems) are set up for different client organizations. With a multitenant architecture, a software application is designed to virtually partition its data and configuration so that each client organization works with a customized virtual application instance
*** Economics of Multitenancy ***
Cost Savings
Multitenancy allows for cost savings over and above the basic economies of scale achievable from consolidating IT resources into a single operation.An application instance usually incurs a certain amount of memory and processing overhead which can be substantial when multiplied by many customers, especially if the customers are small. Multitenancy reduces this overhead by amortizing it over many customers. Further cost savings may come from licensing costs of the underlying software (such as operating systems and database management systems). Put crudely, if you can run everything on a single software instance, you only have to buy one software license. The cost savings can be eclipsed by the difficulty to scale single instance (a bigger faster server can only take you so far) as the demand grows. In addition, the actual development of a multitenancy system is somewhat more complex, and the testing necessary for security needs to be more stringent.
Data Aggregation/Data Mining
One of the most compelling reasons for vendors/ISVs to utilize multitenancy is for the inherent data aggregation benefits. Instead of collecting data from multiple data sources, with potentially different database schemas, all data for all customers is stored in a single database schema. Thus, running queries across customers, mining data, and looking for trends is much simpler. This reason is probably overhyped as one of the core multi-tenancy requirements is the need to prevent Service Provider access to customer (tenant) information.
Complexity
Because of the additional customization complexity and the need to maintain per-tenant metadata, multitenant applications require a larger development effort.
Release Management
Multitenancy simplifies the release management process. In a traditional release management process, packages containing code and database changes are distributed to client desktop and/or server machines. These packages then have to be installed on each individual machine. With the multitenant model, the package typically only needs to be installed on a single server. This greatly simplifies the release management process.
AI
