skip to Main Content

Modern Serverless Development Part 5 – Authentication with Azure Active Directory B2C

Azure Active Directory B2C (Business to Customer) is an identity management service that enables you to customise and control how customers sign up, sign in, and manage their profiles when using an application. Azure Active Directory B2C enables these actions while protecting the identities of your customers at the same time. 
Read More

About Azure SQL Database Managed Instance

The purpose of this article is to discuss what Azure SQL Database Managed Instance is. This will then lay a foundation to explore the capabilities of this deployment model. We will discuss some advantages it can bring to your infrastructure with a cross comparison against on-premises SQL Server. Finally, we look at some important networking configuration that you will need to be aware of when evaluating it.
Read More

Modern Serverless Development Part 4 – Web Application Using Angular 5

Once the data and API layers were in place, the next area to focus on was the client-side. This is a browser-based application and we would use HTML, CSS and Javascript to render the API calls to the user. In fact, due to the nature of the application, the majority of the logic would be held in this layer, so it was a natural step to choose a framework that would enable quality testing and enable easier integration with additional modules.
Read More

Modern Serverless Development Part 3 – Business Logic with Azure Functions

After starting with the database, we moved on to how to expose this data and add our business logic. Our traditional approach would have been to use a Web API but Azure Functions offered a way to completely remove any infrastructure management and scale instantly. It also offered the potential to use micro billing and only pay for calls being made although at a performance cost – more on that later.
Read More

Modern Serverless Development Part 2 – Data Repository with Cosmos DB and Azure Storage

The first decision we made with the new application was to go with a Document Database and for performance and scalability reasons, Azure Cosmos DB was the natural choice. The application would have few related objects and so lent itself to the Document DB model although it would not be likely to the scale to the size where it was a no-brainer.
Read More
Back To Top