Stamps operate independently of each other and can be deployed and updated independently. Each scale unit will host and serve a subset of your tenants. To avoid these issues, consider grouping resources in scale units and provisioning multiple copies of your stamps. To architect for low latency, or to comply with data sovereignty requirements, you might deploy some of your customers into specific regions.
Geographical or geopolitical restrictions.It might make sense to have these customers deployed to isolated environments. You might have some customers who are tolerant of having frequent updates to your system, while others might be risk-averse and want infrequent updates to the system that services their requests. You might need to deploy updates to your service in a controlled manner, and to deploy to different subsets of your customer base at different times. You might also have a pool of smaller customers who can share a multi-tenant deployment. You might have some large customers who need their own independent instances of your solution. Handling single- and multi-tenant instances.Similarly, you might have some customers that require more system resources to service than others, and consider grouping them on different sets of infrastructure. You might need to keep certain customers' data isolated from other customers' data. Similarly, Azure Front Door has higher per-domain pricing when a high number of custom domains are deployed, and it might be better to spread the custom domains across multiple Front Door instances. For example, you might use a database and discover that the marginal cost of adding more capacity (scaling up) becomes prohibitive, and that scaling out is a more cost-effective strategy. Instead, there can be a sudden decrease in performance or increase in cost once a threshold has been met. Some of your solution's components might not scale linearly with the number of requests or the amount of data. For example, you might use services that have limits on the number of inbound connections, host names, TCP sockets, or other resources. Deploying a single instance of your application might result in natural scaling limits. If you host a single instance of your solution, you might be subject to the following limitations:
One key thing to keep in mind is the performance and reliability of your application. When hosting an application in the cloud, there are certain considerations to be made. This approach can improve the scalability of your solution, allow you to deploy instances across multiple regions, and separate your customer data. Multiple stamps can be deployed to scale the solution almost linearly and serve an increasing number of tenants. In a multi-tenant environment, every stamp or scale unit can serve a predefined number of tenants. Each individual copy is called a stamp, or sometimes a service unit, scale unit, or cell. The deployment stamp pattern involves provisioning, managing, and monitoring a heterogeneous group of resources to host and operate multiple workloads or tenants.
0 kommentar(er)
