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

Tracking DevOps initiatives in the backlog

All initiatives and activities performed as part of DevOps must be tracked using the backlog. This is the only way that effort can be prioritized within the stipulated timeframe to accomplish the desired goals.

As an example, we have demonstrated how easily you can capture these initiatives in the form of a backlog under an epic within Azure DevOps:

Figure 7.11 – Tracking DevOps activities as a backlog in Azure DevOps

Tracking everything as a backlog will offer the ability to prioritize tasks for the available capacity. If it's not in the backlog, it will never get done.