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)
1
Section 1: API-Led Architecture in the Digital Economy
4
Section 2: Build Reliable API-Centric Solutions
10
Section 3: Deliver Business Value for a Modern Enterprise

Architecture Tradeoff Analysis Method (ATAM)

Simply put, the ATAM process is a technique that can be used to find the right tuning of the various quality attributes to achieve the optimal quality for the given context.

You can read more about the ATAM process at https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=5177.

The outputs of the ATAM review process are the following:

  • An advisory, a recommendation, or a waiver for the target architecture based on the prioritized list of quality attributes
  • Identification of the architecture risks that may have a high impact
  • A record of the key architecture decisions in support of the suggested solution approach

Thus, we find that ATAM is a crucial and critical activity that must be carried out while defining the architecture of even API platforms. It is important to note that architecture can evolve or change over a period and having a record of the decisions will give a better perspective to the teams...