Cloud

Azure Functions vs Web Jobs vs Cloud Services

Azure Functions vs Web Jobs vs Cloud Services

So you have a web app up and running in Azure and now you need to do some background work that’s related to your new web site but it definitely doesn’t belong in the web app itself. This could be anything from importing data, to sending out subscription emails, to updating cached data, or running database maintenance.

You may be wondering, with so many viable options at your fingertips in Azure, what is the best and most cost effective way to get work done? You want to strike the balance between having something that’s powerful enough to grow if it needs to grow but you don’t want to incur a bunch of unnecessary costs right out of the gate by choosing too much power!

Up and Running with Azure Event Hubs

Up and Running with Azure Event Hubs

This past month I finally had a business case that called for Azure Event Hubs to be part of my overall solution to a real-world problem.  Up until this point I was always able to get by mostly with plain old Table Storage Queues and sometimes Service Bus Topics, but the business case I started working on this past month involved sending many megabytes of information from potentially thousands of devices around the clock.

Paging Results with DocumentDB

Paging Results with DocumentDB

DocumentDB is a great NoSql database engine for working with big data.  One thing that was difficult to implement though was an intelligent way to page through the results.  In this article I will show how I used a combination of caching at the client side of my app along with utilizing continuation tokens from the SDK response to build a decent paging mechanism for big data queries using DocumentDB.

Building Big Data on Azure Table Storage

Building Big Data on Azure Table Storage

When I accepted the position as Director of Business Intelligence at 3xLOGIC in 2013 I was immediately tasked with creating a cloud-based exception reporting platform for the retail industry.  The hardest part about taking that challenge on was that the company was operating on a shoe-string budget at the time and there was also almost no help available to me as far as development resources.  I was going to have to build the entire app - front-end, back-end, database, cloud processes - almost entirely on my own.