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

Evolve architecture blueprints iteratively

Architecture blueprints are typically a set of diagrams and supporting documentation that provides a high-level view of the solution being envisaged from a conceptual, logical, and physical or deployment point of view. It captures the relationship between the various components along with the interaction and integration patterns, bearing in mind the various functional and architecture requirements of the solution.

Traditionally, IT architects have followed a big bang kind of approach, attempting to finalize most parts of the architecture before starting any development work. The primary goal was to identify most of the risks upfront, and then mitigate them before any significant investment of time was done. However, in recent times, the approach for the architecture definition process has shifted from this conventional big bang style to a more experiment, learn, and improve model:

Figure 3.1 – Agile Architecture...