Book Image

Hands-On RESTful API Design Patterns and Best Practices

By : Anupama Murali, Harihara Subramanian J, Pethuru Raj
Book Image

Hands-On RESTful API Design Patterns and Best Practices

By: Anupama Murali, Harihara Subramanian J, Pethuru Raj

Overview of this book

This book deals with the Representational State Transfer (REST) paradigm, which is an architectural style that allows networked devices to communicate with each other over the internet. With the help of this book, you’ll explore the concepts of service-oriented architecture (SOA), event-driven architecture (EDA), and resource-oriented architecture (ROA). This book covers why there is an insistence for high-quality APIs toward enterprise integration. It also covers how to optimize and explore endpoints for microservices with API gateways and touches upon integrated platforms and Hubs for RESTful APIs. You’ll also understand how application delivery and deployments can be simplified and streamlined in the REST world. The book will help you dig deeper into the distinct contributions of RESTful services for IoT analytics and applications. Besides detailing the API design and development aspects, this book will assist you in designing and developing production-ready, testable, sustainable, and enterprise-grade APIs. By the end of the book, you’ll be empowered with all that you need to create highly flexible APIs for next-generation RESTful services and applications.
Table of Contents (13 chapters)

Demystifying the RESTful services paradigm

This book takes a deep dive into RESTful services and APIs. Despite being simple, REST is a fully-featured architectural style. Producing, exposing, and sustaining high-quality RESTful APIs to achieve smooth functional integration is a crucial yet challenging job for IT professionals. Predominantly, REST is implemented with the HTTP protocol. However, REST is not tied to HTTP alone. REST APIs are implemented for a resource, and the resource can be an entity or a service. These APIs provide a way to identify a resource by its URI. URIs can be used to transfer the current state of a resource representation. APIs can be represented as a set of endpoints stuffed with verbs and nouns. A verb typically represents an action, such as get, put, or delete, while the nouns indicate arguments appropriate to the action. It's always a good practice...