Book Image

Designing API-First Enterprise Architectures on Azure

By : Subhajit Chatterjee
Book Image

Designing API-First Enterprise Architectures on Azure

By: Subhajit Chatterjee

Overview of this book

API-centric architectures are foundational to delivering omnichannel experiences for an enterprise. With this book, developers will learn techniques to design loosely coupled, cloud-based, business-tier interfaces that can be consumed by a variety of client applications. Using real-world examples and case studies, the book helps you get to grips with the cloudbased design and implementation of reliable and resilient API-centric solutions. Starting with the evolution of enterprise applications, you'll learn how API-based integration architectures drive digital transformation. You'll then learn about the important principles and practices that apply to cloud-based API architectures and advance to exploring the different architecture styles and their implementation in Azure. This book is written from a practitioner's point of view, so you'll discover ideas and practices that have worked successfully in various customer scenarios. By the end of this book, you'll be able to architect, design, deploy, and monetize your API solutions in the Azure cloud while implementing best practices and industry standards.
Table of Contents (14 chapters)
Section 1: API-Led Architecture in the Digital Economy
Section 2: Build Reliable API-Centric Solutions
Section 3: Deliver Business Value for a Modern Enterprise

The ISO 25010 standard for software product quality

ISO (International Standards Organization) 25010:2011 defines the Systems and software Quality Requirements and Evaluation (SQuaRE) that applies to software engineering. The standard covers two models: a Quality in Use model, and a Product Quality model. This section primarily focuses on the latter model as it applies to the design of API-led solution architectures.

So, what is a quality attribute? In simple terms, it can be viewed as a goal or a requirement that a system must achieve for its acceptance by the various stakeholders and users of the system.

The quality in use model

The quality in use model is more appropriate to consider when building UI applications. It is very important for an overall end-to-end solution, as it focuses on user-centric attributes such as effectiveness, efficiency, satisfaction, safety, and context comprehensiveness. There is some degree of correlation with the product quality model. However...