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

Messages and queues

Commands are messages. This is a way to distinguish the kind of information that describes the actions on an entity, instead of describing the state of an entity. Messages describe the cause and effect of an action over an entity.

Command messages are time-bound, that is, the time in a command is described when a command is issued but not yet executed.

Commands bring arguments necessary to execute the action on the entity.

As data, messages need to be persisted. The point is that a traditional store (such as a database, as we normally refer to them) normally handles entity states, but this is not useful because it would not be optimized to the specific features of the messages:

  • Messages are useful only if correctly ordered in time; messaging systems handle unordered messages as an issue

  • Messages should be handled once

  • Message execution should be idempotent, that is, executing a message twice should not affect the system the second time

  • Messages should be marked as consumed