Let’s imagine a web application where, for each request, it must read configuration data from a database. That data doesn’t change usually, but the application, in each request, must connect, execute the correct instructions to read the data, pick it up from the network, etc. Imagine also that the database is very busy or the connection is slow. What would happen? We would have a slow application because it is reading continuously data that hardly changes. A solution to that problem could be using a cache within the Spring framework.
Spring caching is based on a simple principle: