Book Image

RESTful Java Web Services - Third Edition

By : Balachandar Bogunuva Mohanram, Jobinesh Purushothaman
Book Image

RESTful Java Web Services - Third Edition

By: Balachandar Bogunuva Mohanram, Jobinesh Purushothaman

Overview of this book

Representational State Transfer (REST) is a simple yet powerful software architecture style to create lightweight and scalable web services. The RESTful web services use HTTP as the transport protocol and can use any message formats, including XML, JSON(widely used), CSV, and many more, which makes it easily inter-operable across different languages and platforms. This successful book is currently in its 3rd edition and has been used by thousands of developers. It serves as an excellent guide for developing RESTful web services in Java. This book attempts to familiarize the reader with the concepts of REST. It is a pragmatic guide for designing and developing web services using Java APIs for real-life use cases following best practices and for learning to secure REST APIs using OAuth and JWT. Finally, you will learn the role of RESTful web services for future technological advances, be it cloud, IoT or social media. By the end of this book, you will be able to efficiently build robust, scalable, and secure RESTful web services using Java APIs.
Table of Contents (11 chapters)

A quick recap

Having gone through in detail of various design guidelines in preceding sections, let's do a quick recap of the best practices as applicable to each of the key focus areas:

Focus area Best practices
Resource
  • Expose only those resources that are required for implementing the business use case
  • Naming of resource must be nouns; avoid using verbs
  • Avoid using generic name for resources, rather be specific
  • Resource names may include hyphens; avoid using underscores and other punctuation
  • Limit the length of the resource URI not to exceed 2,000 characters
  • Child resource must limit the scope to respective parent
Resource representation
  • Specify the content type supported by consumers of the API
  • Avoid using multiple content type for a resource representation, JSON is becoming the de facto standard for content type, so avoid using XML
  • Include Content-Type header...