Skip to main content

Why to use Azure Databricks to run your Apache Spark Notebooks

By
A few months ago (almost one year) a new flavor of Apache Spark appeared on Microsoft Azure. Azure Databricks it is just a platform optimized for Azure, where Apache Spark can run.
The consumer does not need anymore to configure the Apache Spark cluster (VM creation, configuration, network, security, storage and many more). Azure Databricks already has a cluster that is configured and ready to be used. We can focus on our application and business requirements and less on the infrastructure part.

Capabilities and Features
All the features that we have inside Apache Spark can also be found inside Azure Databricks. The same version of Spark that you have on-premises runs on top of Azure Databricks, the only difference is at the infrastructure level, where you already have the system preconfigured. As a user, you are free to scale up or down your cluster in a 'drag and drop' manner, without having to pay attention or do anything else.
All the 5 main components of Spark can be found on top of Azure Databricks:

  • Streaming Capability
  • GraphX for data exploration and cognitive analytics
  • MLib for machine learning support
  • Core API for integration with R, Python, Scala, Java, and SQL
  • DataFrames with Spark SQL for working with structured data
A nice feature of Azure Databricks is the capability to remove/terminate a Spark cluster in the moment when the cluster it is not used anymore. When you create a new cluster, you have the option to specify after how many minutes of inactivity the cluster should be terminated. This option is useful especially during the developing phase where you can save a lot of resources in this way without complicated procedures. 

Integration points
At this moment in time, there are integration points with Hadoop Storage, Apache Kafka, Azure SQL Data Warehouse, Azure Data Lake Store and Azure Blob Storage. This in combination with Spark capability to combine data stream with static data makes Apache Spark a super exciting option when you need fast deployment and reliable services. 
As a side note, Azure Databricks it is using Azure Container Services behind the scene.

Scenarios
Even if Spark has an excellent support for ML, Data Analysis and Fog Computing in IoT scenarios, in the most of the cases, Spark it is used for the streaming capabilities, where it is enabling us to ETL on top of data streams, trigger events based on stream content or data enrichment with static content when needed. 
It is a clear trend to do a lot of AI and ML inside Azure Spark that enables us to process and analyze data streams in real-time. 

Pricing
The pricing model of Azure Databricks contains two components:
  1. Azure VM price
  2. DBU (Databricks Unit)
Depending on the cluster size, you will pay for the no. of Azure VM's that you are using inside the cluster. You can specify the type and the number of the VM's that you want to use. The price of the VMs it's the same as for Azure VM with Linux.
DBU represents the processing capability. Based on the type of the VM you will notice that each VM has a different DBU capability. D12 has 1 DBU vs D15 that had 5 DBUs for each node. For each DBU you will an additional amount of money. We can imagine that inside DBU are all other costs of cluster management from configuration and networking to storage and environment optimization. 
For DBU there are two pricing tiers (Standard and Premium). The most significant difference between this two is the Role Base Access control that can be found on the Premium tier. 

What you shall take a look on Azure Databricks?
  1. Autoscaling capability
  2. Auto-termination capability
  3. Optimized by design
  4. Connectors with Azure Services (e.g. Azure Data Lake and Blob Storage)
  5. PowerBI integration
  6. Support for automation
  7. Simple price model
  8. Multiple types of Azure VM supported
  9. Enterprise-ready with Azure AD support
  10. Security and privacy out of the box

Comments

Post a Comment

Popular posts from this blog

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

By
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(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more