Jeremy Likness
Jeremy Likness
Empowering developers to be their best.
📅 Mar 13, 2018 🕘 2 min read 💬 315 words

Use the Serverless Cloud for ETL Scenarios

A real world scenario that leverages Azure Functions

You are viewing a limited version of this blog. To enable experiences like comments, opt-in to our privacy and cookie policy.

The essence of serverless is less server. The details of the server are abstracted away and the developer is able to focus on code without getting bogged down in infrastructure concerns. Extract, Transform, and Load (ETL) is a common scenario in enterprise applications that serverless applications are uniquely positioned to address. Developers are able to handle file uploads, set timers and schedules, and run transformations using serverless without touching hardware, installing third-party services or writing custom polling software.

Common ETL scenario addressed by this walkthrough

Common ETL scenario addressed by this walkthrough

There is a better way! As much as I love to speak and write about serverless, I still believe the best way to learn what it is, and understand its value, is to go hands-on. To give you a full end-to-end scenario, I wrote a walk through and published it to GitHub.

JeremyLikness/azure-fn-file-process-hol

This lab exposes you to the full spectrum of capabilities and workflows associated with serverless application development. You will:

  1. Create a serverless Azure function locally and debug it on your machine (no Internet required) using the cross-platform functions host
  2. Set up a trigger to automatically detect when a file is uploaded to file storage — no polling required (and you’ll also test this locally using the Azure Storage Emulator)
  3. Create a local SQL database that represents a common scenario: the legacy on-premises database
  4. Learn how to use Entity Framework in Azure Functions by parsing a CSV file and inserting new records into the database
  5. Create a cloud-hosted Azure SQL Database and migrate your local database to the cloud
  6. Deploy your local code to Azure
  7. Run the full process entirely from the cloud without configuring a single piece of hardware or consulting with a DBA

If the previous list includes scenarios you are interested in and would like to learn more about, carve out an hour on your schedule and head on over to the hands-on walk through!

Jeremy Likness

Do you have an idea or suggestion for a blog post? Submit it here!
comments powered by Disqus

Related articles: