Skip to main content

Azure SQL Database - Elastic Scale, perfect solution for sharding

There is a great news for people that use Azure SQL Database. Elastic scale is available in preview phase. I expecting this feature from some time and now I’m happy that is available to us.
The biggest advantage of a cloud solution is scalability and pay as you go. You pay a resource only when you need it without paying the period of time when you don’t use it. Over this features, a service like automatically scaling can be added very easily. This is applicable when we are talking about web sites, web/worker roles where things are not so complicated.
To be able to scale the data-tier or an application you need to be able to use sharding (joining multiple resources, in our case splitting a big database on multiple databases). This feature was enabled on Microsoft Azure in a very smart way and without adding additional costs to the end user. You will pay the Azure SQL instances that you use. For each shard you will need to use a new instance of Azure SQL Database.
Elastic scale is enabled from a simple template that is created using Visual Studio. From this project, we can control and manage the shards, shard mapping, query multiple shards and adding additional one if needed.

When we should use sharding?

  • The total data that we want to store into one database is too big. 
  • A part of our database should reside in a specific geographical location (a part in Europe, a part in USA)
  • The number of transactions that are executed over a single database hit the maximum capabilities of one instance
  • There is a need of tenant physical isolation


Key features available in this moment

  • Shard Map Management – It is used to create new shards, manage configuration, specify the key range for shards
  • Data Dependent Routing – Enable to create connection to a specific shard and route that given request
  • Shard Elasticity – Enables us to scale vertical (by control the type of SQL Azure that we are using) or horizontally (adding more shards/removing shards)
  • Multi-Shard Queries – When a SQL hit multiple shards, the system will be smart enough to execute the request on multiple shards and merge the result for us.
  • Split-Merge Service – When we increase, decrease the number of shards, the system will automatically balance the sharding data distribution    

How to get a db connection
To get a connection to a specific database you can specify the ID of the entity. In this way you will get a connection directly to the database where your entity is stored.
ShardMapManager shardManager = ShardMapManagerFactory.GetSqlShardMapManager(
     connectionString, 
     ShardMapManagerLoadPolicy.Lazy);
RangeShardMap<int> fooShardMapping = shardManager.GetRangeShardMap<int>("fooMapper");
SqlConnection fooDbConnection = fooShardMapping.OpenConnectionForKey(fooId, Configuration.GetCredentialsConnectionString(), ConnectionOptions.Validate)
ShardMapManager can be created only once time per application and is used to execute queries on the appropriate database. In this way we don’t need to track the database connection. You can imagine this manager as a connection pool where all connection to databases are tracked.

Conclusion
This is a great feature, that can save your life. Now, sharding can be configured very easily by anyone.

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP