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 Building a RESTful Web Service with Spring
  • Table Of Contents Toc
  • Feedback & Rating feedback
Building a RESTful Web Service with Spring

Building a RESTful Web Service with Spring

By : Ludovic Dewailly
3.7 (15)
close
close
Building a RESTful Web Service with Spring

Building a RESTful Web Service with Spring

3.7 (15)
By: Ludovic Dewailly

Overview of this book

REST is an architectural style that tackles the challenges of building scalable web services. In today’s connected world, APIs have taken a central role on the web. APIs provide the fabric through which systems interact, and REST has become synonymous with APIs. The depth, breadth, and ease of use of Spring makes it one of the most attractive frameworks in the Java ecosystem. Marrying the two technologies is therefore a very natural choice. This book takes you through the design of RESTful web services and leverages the Spring Framework to implement these services. Starting from the basics of the philosophy behind REST, you’ll go through the steps of designing and implementing an enterprise-grade RESTful web service. Taking a practical approach, each chapter provides code samples that you can apply to your own circumstances. This book goes beyond the use of Spring and explores approaches to tackle resilience, security, and scalability concerns. You’ll learn techniques to deal with security in Spring and discover how to implement unit and integration test strategies. Finally, the book ends by walking you through building a Java client for your RESTful web service, along with some scaling techniques for it.
Table of Contents (12 chapters)
close
close
11
Index

Updating resources


Choosing URI formats is an important part of designing RESTful APIs. As seen earlier, rooms are accessed using the path, /rooms/{roomId}, and created under /rooms. And you might recall that as per the HTTP specification, PUT requests can result in creating entities if they do not exist. The decision to create new resources on update requests is up to the service designer. It does, however, affect the choice of path to use for such requests.

Semantically, PUT requests update entities stored under the supplied request URI. This means that update requests should use the same URI as GET requests: /rooms/{roomId}. However, this approach hinders the ability to support resource creation on update, since no room identifier is available.

The alternative path we can use is /rooms, with the room identifier passed in the body of the request. With this approach, PUT requests can be treated as POST requests when the resource does not contain an identifier.

Given that the first approach...

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.
Building a RESTful Web Service with Spring
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