Gain insights into building scalable applications with Thymeleaf and Spring Boot. Delve into Spring Data, Spring Security, and testing methods to ensure maintainable, portfolio-worthy projects.

maven.tar.gz

13SepBackgroundPostGres

DockerCompose14Sep

OptimizedMvn-22Sep

Moving into root - 24 Sep

From GitHub Repo - 12.4 - 24 Sep

Built from Github and running directly without watcher - 30Sep

Watcher - 29 Sep

From usercode directly - Oct 1

DockerCompose14Sep-Chapter09

OptimizedMvn-22Sep-Chapter11

DockerCompose14Sep-Chapter09-copy

Chapter09-Testing

Cypress

Chapter17-Testing

Cypress-copy

Integration Testing

Initial Chapters

Initial Chapters-copy

Watcher

Initial Chapters-Watcher

Integration Testing-copy

In this course, you will learn how to build easily scalable applications with Thymeleaf and Spring Boot. More specifically, you will combine Thymeleaf and Spring Boot with Spring Data and Spring Security. In a nutshell, this course will give you all the basics you need to start developing an application using Thymeleaf and Spring Boot.

Throughout the course, you will be building an application of a fictional basketball team called Thyme Wizards. Additionally, you will also learn to use unit and integration tests to ensure the proper code functionality and build a maintainable codebase that you can expand upon.

By the end, you will have a new project to add to your portfolio and some great new skills that employers will love.

Building Scalable Applications with Thymeleaf and Spring Boot

We'll be dealing with both `...Parameter` classes and `...FormData` classes throughout the course. Let's understand the difference between the two.

## FormData
- A `FormData` class is always used as a form backing object for an HTML form. 
- It will typically be mutable, as Spring MVC needs to bind the changes from the form on the object.
-  It will not throw `NullPointerException` or `IllegalArgumentException` when there is invalid data, because the class exists to model invalid data entered by a user in a form. We need to have that invalid data when we re-render the page to show what is wrong and give the user a chance to fix their mistake.
- It will also typically use `String` typing since that is easy to use for binding. It is part of the web layer within the feature package and should only be used by the controller.

## Parameters
- A Parameters object is part of the domain layer. Such objects will be immutable and they will validate all constructor arguments, throwing `NullPointerException`, `IllegalArgumentException` or other exception types as needed.
- An additional advantage of a `Parameters` object is that we can use it as an alternative to having each possible parameter in the method signature.

Learn the difference between parameters and FormData objects.

Parameters vs. FormData objects

Getting Started

What are Spring Boot and Thymeleaf?

Thymeleaf Introduction

Thyme Wizards

Fragments

Layouts

Controllers

Internationalization

Database Connection

Displaying Data

Forms

Data Editing

Implement Deletion of an Entity

Security

Security - Users from Database

Develop Microservices Using Spring Boot

Testing

Testing Using Cypress

Various Tips and Tricks - I

Various Tips and Tricks - II

Spring Boot and Thymeleaf Tutorial: Build a Recipe Sharing App

Conclusion

Appendix

Parameters vs. FormData objects