Book Image

Azure Integration Guide for Business

By : Joshua Garverick, Jack Lee, Mélony Qin, Trevoir Williams
Book Image

Azure Integration Guide for Business

By: Joshua Garverick, Jack Lee, Mélony Qin, Trevoir Williams

Overview of this book

Azure Integration Guide for Business is essential for decision makers planning to transform their business with Microsoft Azure. The Microsoft Azure cloud platform can improve the availability, scalability, and cost-efficiency of any business. The guidance in this book will help decision makers gain valuable insights into proactively managing their applications and infrastructure. You'll learn to apply best practices in Azure Virtual Network and Azure Storage design, ensuring an efficient and secure cloud infrastructure. You'll also discover how to automate Azure through Infrastructure as Code (IaC) and leverage various Azure services to support OLTP applications. Next, you’ll explore how to implement Azure offerings for event-driven architectural solutions and serverless applications. Additionally, you’ll gain in-depth knowledge on how to develop an automated, secure, and scalable solutions. Core elements of the Azure ecosystem will be discussed in the final chapters of the book, such as big data solutions, cost governance, and best practices to help you optimize your business. By the end of this book, you’ll understand what a well-architected Azure solution looks like and how to lead your organization toward a tailored Azure solution that meets your business needs.
Table of Contents (15 chapters)

OLTP applications

OLTP applications help in the processing and management of transactions. Some of the most widely used OLTP implementations can be found in retail sales, financial transaction systems, and order entry. These applications perform data capture, data processing, data retrieval, data modification, and data storage. Let’s dive into transactional data a bit further.

Transactional data

The capture and usage of data that encompasses a record of business interaction is generally referred to as a transaction. Information related to creating purchase orders, sales at a cash register, a deposit at a bank, or collection of a bus fare can all be considered transactional. Systems that manage this type of data can vary in size dependent on the volume of transactions handled, as well as regional location requirements, the structure of data being stored, the security requirements for storing and processing the data, or consistency requirements that mandate near-real-time...