Book Image

Building RESTful Web Services with Spring 5 - Second Edition

By : Raja CSP Raman, Ludovic Dewailly
Book Image

Building RESTful Web Services with Spring 5 - Second Edition

By: Raja CSP Raman, 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 second edition brings forth the power of the latest Spring 5.0 release, working with MVC built-in as well as the front end framework. It then goes beyond the use of Spring to explores approaches to tackle resilience, security, and scalability concerns. Improve performance of your applications with the new HTTP 2.0 standards. 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 using the new Spring Reactive libraries.
Table of Contents (21 chapters)
Title Page
Copyright and Credits
Packt Upsell
Spring Security and JWT (JSON Web Token)

Monolithic architecture and its drawbacks

Even though microservice architecture is growing in popularity nowadays, the majority of companies still use the monolithic architecture. As a monolithic application, you can bundle all business modules into one single unit and deploy them in all desired servers. If any changes are needed in the application, developers have to provide them and redeploy the updated version of the application. In monolithic, we follow tight coupling between service modules.

Though monolithic architecture has some benefits, its drawbacks paved the way for an alternate architectural design—microservices. Here we will talk a little about the drawbacks of monolithic architecture:

  • For each bug fix or code change, we have to redeploy the entire application on all servers
  • If any common issue persists in the monolithic application, such as performance issues, it will impact the entire application, which might be hard to find out and fix quickly
  • Bigger applications might take longer...