Skip to main content

From Azure Data Factory to Event Hub and Functions

There are cases when we cannot use cloud service as in the book. Even if in theory the mapping between the technical needs and the functionality of the cloud service is perfect, we could have external factors that influence the way how we design the solution.  
You should remember all the time to check all current context, team shape, and client preferences before building a solution.

Context
Imagine that you need to build a solution that would fetch data from an Azure SQL Database, do some transformation and push content to an on-premises database over HTTPS. 

Initial Solution
When you read the high-level reqs you already see an ETL solution, that would be translated into an Azure Data Factory that load data from SQL Database, to some transformation and make HTTPS requests. 

Team shape
Azure Data Factory integration with SSIS packages enables us to build an ETL seamless, using the team knowledge that already exists on SQL Server and SSIS. When the team technology stack is Java and Oracle, you might look at a different solution.
The logic components (e.g. data transformation) are moved from SSIS packages to Azure Functions that are automatically triggered by Azure Data Factory Pipelines. Even if the solution is changed a little bit, Azure Data Factory remains a strong candidate.


HTTPS Requests
To be able to do HTTP requests to on-premises systems, Azure Data Factory requires to have an IR (Integration Runtime). You just find out that even if you have HTTPS, REST API, and Web Table connector when you need to do HTTPS requests that are not pointing to Azure Services you need to configure a self-hosted IR.
The self-hosted IR runs on an Azure Virtual Machine that you need to deploy and install an agent. Data Factory can create automatically the self-hosted IR by itself, but even so, you end up with additional VMs. The IR is used by Azure Data Factory do execute the HTTPS requests to on-premises applications. 
At this moment in time, Azure Data Factory plays the role of the orchestrator between Azure Functions, IR and data movement. 


Data Source and Data Content
Things become more complex when the data sources from where content needs to be pushed to the on-premises system are not only Azure SQL Database. There places in code, that need to trigger data to be pushed to on-premises. 
In addition to this, specific changes to data that it is stored in Azure SQL Database needs to trigger such a push to on-premises. Some of them are hard to catch from SQL and in most cases, the ''signal' comes from application logic. It is not enough to specify to the Pipeline to push content that was modified from the last run. You need also additional logic that needs to decide what data needs to be pushed. 

Redesign
Most of the transformation logic is inside Azure Functions. The pipelines need to fetch data from multiple sources and near-real-time becomes a requirement. Taking this into account, we can redesign the solution as you can see below.
The part of the logic that do the transformation and calls the on-premises system is stored inside Azure Functions. Azure Event Hub is used to collect all the data that needs to be pushed to the on-premises systems.
There a gate logic implemented at the application level that automatically pushes data to Azure Event Hub when specific content needs to deliver to the on-premises system.

As we can see the end solution looks different in comparison with the first one. Even so, it does its job well and is a perfect match with team shape, requirements and future enhancements. 



  





Comments

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