Book Image

Mastering Cloud Development using Microsoft Azure

Book Image

Mastering Cloud Development using Microsoft Azure

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
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

Writing catalogs into Azure DocumentDB


One of the features of a catalog is accessing the product list and details the company sells. There is a big difference between read and write operations, favoring the first one as the most frequent. At the web stage, write operations happen only when the catalog is updated, and publishing involves just a minimal time (seconds to minutes) compared to using them (days to weeks). So, if indexing operations take a while to succeed, it is not bad. Eventual consistency is not an issue.

Product information is not flat. It is complex and structured, as information such as categorization, technical properties, and localization are not scalar properties, but complex structure themselves. Many products share the same categories or information. Again as mentioned earlier, write operations happen as catalog publishing, not product insertion. So, there are no normalization issues, as the product is already managed into the relational database-based ERP. On the other...