{"id":2628,"date":"2016-05-27T23:26:36","date_gmt":"2016-05-28T03:26:36","guid":{"rendered":"http:\/\/springframework.guru\/?p=2628"},"modified":"2019-05-11T14:10:26","modified_gmt":"2019-05-11T18:10:26","slug":"accessing-database-thymeleaf-template","status":"publish","type":"post","link":"https:\/\/springframework.guru\/accessing-database-thymeleaf-template\/","title":{"rendered":"Accessing the Database from a Thymeleaf Template"},"content":{"rendered":"

This week, I had a student ask me how they could use a Java function to access the database from a Thymeleaf template. Thymeleaf is a modern templating engine. And accessing the database directly from Thymeleaf is certainly something you could do. But is it really something you want to do?<\/p>\n

I’ve worked for a couple major retailers which had JSP templates accessing the database with static Java methods. It was not a good thing.<\/p>\n

When you’re using Thymeleaf with Spring MVC, you’re following the MVC design pattern. MVC is Model, View, Controller. The Thymeleaf template is the ‘View’. The Spring controller will return a model to the Thymeleaf template engine. The model should be a data structure. Nothing more.<\/p>\n

\"Spring<\/a>The MVC design pattern is elegant and widely accepted design pattern. I personally like how the MVC design pattern is in alignment with the SOLID Principles of Object Oriented Design<\/a>.<\/p>\n

If you choose to access the database directly from Thymeleaf, you break the separation of concerns. You’re violating the SOLID principles of Object Oriented Design.<\/p>\n

I took the time to record a brief video about why accessing the database from Thymeleaf is a very bad idea. You can see the video here on YouTube.<\/p>\n

<\/div><\/div>
<\/div>
<\/div>
<\/div><\/div><\/div>