Shulou(Shulou.com)05/31 Report--

What this article shares with you is what is the core design idea of supporting multi-tenant Multi tenant on the Salesforce platform. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

Multi-tenant technology is the basic technology used by the cloud to share IT resources cost-effectively and securely.

Multi-tenant support is a technology that all cloud service providers need to implement, which is used to share IT resources on cloud infrastructure under the premise of controllable cost and security.

Four challenges for multi-tenant support:

How to keep tenant-specific data secure in a shared database so that one tenant can't see another tenant's data?

How to ensure the data isolation between different tenants in the shared database? generally speaking, a tenant should not see the data of other tenants.

When a tenant adjusts its own schema object or API, it should not affect the functionality of other tenants and the availability of the entire system.

How can one tenant customize various schema objects and an application's user interface in real time without affecting the functionality or availability of the system for all other tenants?

How can the system's code base be patched or upgraded without breaking tenant-specific schemas?

Changes in the grass-roots implementation of the system, such as code version upgrades, or when new patches come in, should not destroy each tenant's private objects.

And how will the system's response time scale as tens of thousands of tenants use the service?

With the increase in the number of system tenants, the response time of the whole system should not decrease sharply.

Force.com's core technology uses a runtime engine that materializes all application data from metadata-data about the data itself. In Force.com's well-defined metadata-driven architecture, there is a clear separation of the compiled runtime database engine (kernel), tenant data, and the metadata that describes each application. These distinct boundaries make it possible to independently update the system kernel and tenant-specific applications and schemas, with virtually no risk of one affecting the others.

Salesforce is designed to address these challenges by adopting a run-time engine approach in which all application data is generated through metadata, the so-called metadata-driven architecture (metadata driven architecture). In this way, the metadata of the model, as input, is handed over to the runtime engine for processing to generate the model and data used at run time, each of which has its own duties and strict distinction, and achieves a highly dynamic kernel.

These are the core design ideas of the Salesforce platform to support multi-tenant Multi tenant. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.