Data-tier
The simplest data tier is the so-called per-single or individual database. This is pretty easy to explain and understand: create an Azure SQL database, for example, within an Sx tier, and, if a customer needs more performance, you just have to scale it up to Sx+n, depending on how many resources you need (how fast you want your process to finish).
The drawback with individual databases is that, by the time you have created the database in Azure SQL, all the resources are allocated, not shared nor released, and the customer – or you – has to pay for them, whether you are using them or not.
When you have thousands (or hundreds of thousands) of databases to handle, like in every multi-tenant class A product, the resource placement ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access