Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Designing API-First Enterprise Architectures on Azure

You're reading from   Designing API-First Enterprise Architectures on Azure A guide for architects and developers to expedite digital transformation with API-led architectures

Arrow left icon
Product type Paperback
Published in Aug 2021
Publisher Packt
ISBN-13 9781801813914
Length 290 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Subhajit Chatterjee Subhajit Chatterjee
Author Profile Icon Subhajit Chatterjee
Subhajit Chatterjee
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Section 1: API-Led Architecture in the Digital Economy
2. Chapter 1: Evolution of Enterprise Solution Architectures FREE CHAPTER 3. Chapter 2: APIs as Digital Connectors 4. Section 2: Build Reliable API-Centric Solutions
5. Chapter 3: Architecture Principles and API Styles 6. Chapter 4: Assuring the Quality of the API Service (or Product) 7. Chapter 5: RESTful APIs – the New Web 8. Chapter 6: API Design Practices 9. Chapter 7: Accelerating through DevOps Essentials 10. Section 3: Deliver Business Value for a Modern Enterprise
11. Chapter 8: API-Centric Enterprise Integrations 12. Chapter 9: APIs as a Monetized Product 13. Other Books You May Enjoy

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...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image