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

Finding the right style for your API use cases

When it comes to building API platforms, there is no one-size-fits-all. While certain styles are more modern and widely used, but each style has its limitations as well. Hence, the API development teams must evaluate the key scenarios carefully and apply some sort of weighted matrix to understand the pros and cons in order to determine the best style for the specific use case.

There is a usual tendency among developers to make use of experience and programming language familiarity while approaching API requirements for any newer projects. However, this approach is fraught with challenges when it comes to the extensibility of API platforms. So, you must always do a thorough analysis to select the right style for your needs.

You may want to consider the following guidance while selecting the API style for your use cases:

The preceding list of use cases is not comprehensive and is provided as guidance only...