Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Designing API-First Enterprise Architectures on Azure
  • Table Of Contents Toc
  • Feedback & Rating feedback
Designing API-First Enterprise Architectures on Azure

Designing API-First Enterprise Architectures on Azure

By : Subhajit Chatterjee
4.6 (20)
close
close
Designing API-First Enterprise Architectures on Azure

Designing API-First Enterprise Architectures on Azure

4.6 (20)
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)
close
close
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

Chapter 4: Assuring the Quality of the API Service (or Product)

All software engineering teams strive to create a quality product as an output from the weeks of planning, designing, developing, and testing cycles. This, however, is not possible unless there is a clear and common understanding of the quality goals (or attributes) of the product under development.

A product backlog in the form of architecture backlog stories must be created and prioritized in a timely fashion to accomplish the targets/metrics set for these quality attributes. Otherwise, late discovery of critical issues, and subsequent fixing at a later stage in the project lifecycle, will turn out to be very costly.

The purpose of this chapter is to understand the important quality attributes that will apply to API-centric solutions. The objective is to assess the impact of non-functional requirements on the solution design and what trade-offs are necessary to achieve a highly reliable API platform.

By the...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Designing API-First Enterprise Architectures on Azure
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon