Book Image

Mastering Cloud Development using Microsoft Azure

By : Roberto Freato, Marco Parenzan
Book Image

Mastering Cloud Development using Microsoft Azure

By: Roberto Freato, Marco Parenzan

Overview of this book

Microsoft Azure is a cloud computing platform that supports many different programming languages, tools, and frameworks, including both Microsoft-specific and third-party software and systems. This book starts by helping you set up a professional development environments in the cloud and integrating them with your local environment to achieve improved efficiency. You will move on to create front-end and back-end services, and then build cross-platform applications using Azure. Next you’ll get to grips with advanced techniques used to analyze usage data and automate billing operations. Following on from that, you will gain knowledge of how you can extend your on-premise solution to the cloud and move data in a pipeline. In a nutshell, this book will show you how to build high-quality, end-to-end services using Microsoft Azure. By the end of this book, you will have the skillset needed to successfully set up, develop, and manage a full-stack Azure infrastructure.
Table of Contents (15 chapters)
Mastering Cloud Development using Microsoft Azure
About the Authors
About the Reviewer

Per-stream event handling

We learned that an event is the notification of the execution of a command. In general, any action, not only a command execution with workers and queues, can notify events. The purpose is to react (or not) to the event with some tasks and this decision is completely decoupled from the task that has generated it. Note that in this way, we decide if and how by looking just at a single event.

There are some scenarios where we might take decisions because of a group of events that are raised in a period of time. Let's take the login process of a web application as an example.

A user types their username and password into the login form to perform authentication. Authentication fails. The effect of this action is to raise an invalid login event. We are used to locking out a username after three invalid login attempts. We typically implement this process, counting the number of login attempts and storing the counter into the username profile. When login fails and the counter...