In your Spring MVC application, you will usually have at least one endpoint which accepts and ID as a path variable or request parameter, and often the next thing you will do is to load the model from your Spring Data repository. However, there is an easier way as you will see in a minute.
In this tutorial, I show you an easy way for handling pagination when you use Spring Data and Spring MVC in your application you might not be aware of.
In my Spring Boot workshop last week one of the participants asked me to clarify what Spring Data actually is. He came from a different background and was confused how Spring Data, JPA, Hibernate and NoSQL relate and what role Spring Data plays. Indeed, if you switch contexts, it may look strange at first. However, it is not, and I write today the same I answered in the workshop.
One of the many things Spring Data offers is a basic auditing functionality. It is great if you only need to track who made changes to your model and when. So, let’s stop the talking and dive into it.
Working with Spring Data has the huge benefit that you work with a common interface regardless of the underlying storage medium. Yet, it’s still transparent enough. In today’s tutorial, we will use it with a MongoDB.
There’s an easy way to build a REST API for your Spring Data repositories instantly. It doesn’t matter if you are using JPA, MongoDB or any of the other stores available with Spring Data. Spring Data REST is the little helper. In this tutorial, we will take a closer look at how you can use it.