Henry Been is an independent DevOps and Azure architect from The Netherlands. He enjoys working with development teams to create and deliver great software. For him, this includes the full DevOps cycle, starting from discovering and planning new features and ending only when end-users are satisfied. Henry’s interests include the Azure cloud, DevOps, software architecture and the design and implementation of testable and maintainable software. Next to his work, he is one of the Microsoft ALM DevOps Rangers, a group of 130 engineers worldwide who share professional guidance and create gap filling solutions surrounding VSTS and Azure.
How to build a multi-tenant SaaS application using 60.000 Azure SQL Databases.
Developers designing a large scale cloud applications should consider using a database-per-tenant architecture to scale-out their database. This architectural style is ideal for the cloud, providing isolation and security advantages. This session explores this pattern and related Azure offerings.
“To create an application that is truly designed for massive scale, scale-out at every level of the solution is needed.
While doing so at the services level, many developers are still using a single database to serve every request. This way there remains a single point of failure and also a single performance bottleneck. To address this issue, a new architectural style is emerging, enabled by Azure SQL Database Elastic Pools. Using a database per tenant, all data is distributed over a large number of databases.
Having worked with one of the largest of these architectures in the world, Henry Been will explore this pattern in detail, covering its advantages and disadvantages and a number of common scenarios around such an architecture. After this session you should not only understand this pattern, but also be able to decide whether it fits with your scenario or not.”