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

Exploring the checklist for building RESTful APIs

Cloud computing and microservices are almost certain to follow RESTful API design as a rule for its implementations. The stateless nature of these APIs allows these services to be redeployed easily, whenever they're needed.

The following tables serve as a design and implementation checklist for all RESTful API developers:

  • Model domain actions using HTTP methods: Earlier in this chapter, you understood that the operations that are supported by a REST API can be modeled as HTTP operations on a specified resource. Hence, it is a common practice to enumerate the various actions that will be allowed on a domain entity, and then map those different HTTP methods to indicate the operation to be performed on the requested resource, as identified by the request URI:  
  • Ensure that all the supported features are CRUD in nature: RESTful APIs typically update any backend database system...