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
Dedication
Packt Upsell
Contributors
Preface
6
Spring Security and JWT (JSON Web Token)
Index

Logger controls


Logging will be helpful when we need to track the output of a specific process. It will help us verify the process or find the root cause of the error when things go wrong after deploying our application in the server. Without loggers, it will be difficult to track and figure out the problem if anything happens.

There are many logging frameworks we can use in our application; Log4j and Logback are the two major frameworks used in most applications.

SLF4J, Log4J, and Logback

SLF4j is an API to help us choose Log4j or Logback or any other JDK logging during deployment. SLF4j is just an abstraction layer that gives freedom to the user who uses our logging API. If someone wants to use JDK logging or Log4j in their implementation, SLF4j will help them plug in the desired framework during runtime.

If we create an end product that can't be used by someone as a library, we can implement Log4j or Logback directly. However, if we have a code that can be used as a library, it would be better...