Learn how Spring Boot Model Mapper works Fast and Simple

Spring Boot allows you to create Entities that reflect your business model and database, external to your service logic you should not expose those unique properties. In the case of transferring information out to an API for example you should map the contents to a DTO (Data Transfer Object) that may not be exactly what your business entity shape looks like. For example elements like passwords should be excluded and computed properties may not be part of your entities but can be part of your DTO objects.
Learn how to use Mappers in Spring Boot and isolate and add a loosely coupled interfaces that does not break as code changes.
More can be found on my Udemy classes: www.udemy.com/user/tomjay2
Find this and more on my GitHub: github.com/ThomasJay
As well as my Web site: www.thomasjayconsulting.com
I want to help you learn and find an Amazing Job or just increase your Skills.
#Java #SpringBoot #software

[@moisesvillalba6615]

Thanks so much for the great explanation! Greetings from Paraguay, South America

[@edsonjr.1381]

It’s amazing how easly you create these tutorials and I’m really enjoying and helping me out a lot. Please keep creating more videos like this.

[@fatihdeniz3702]

Great Job. Simple and usefull. Thanks

[@johndoedoejohn]

Great video, would love to see more materials on Spring. Personally using mapstruct mapper, quite easy to use and seems to have less boilerplate code. Thank you for this video

[@NeverQuitOk]

What Xavier. Why are you here

[@shahd07072]

That was very good, tank you.

[@namminh4336]

Great lesson

[@naushad30]

Great content

[@user-ql1rg9mj9d]

Is the reason you created the mapperconfig(modelmapper) to do it as a singleton?

[@fastandsimpledevelopment]

Yes, Sprint Beans are Singletons by default so no overhead in creating each mapper objects at runtime after the initial bean creation

[@user-ql1rg9mj9d]

@@fastandsimpledevelopment thank you

[@Wafacooking1]

Hey

[@duongphuba7216]

Omg, why do not you use record UserDto, bro?

[@fastandsimpledevelopment]

This is based on Java 8, records where introduced in Java 14. Java 8 is still used by 99% of the companies I work with.

[@gasparcalix2095]

most of the companys are using java8 to java11.

[@fastandsimpledevelopment]

@@gasparcalix2095 You can not move from Java 8 to anything else and get Oracle support without paying, Banks and Insurance companies do not want to pay for Java. Open JDK does not pass security standards yet. Same issue with Spring Boot 3, you really need a newer version of Java but no one is making the commitment yet and changing out of older dependencies is hard. We still have more years of Java 8 - End of Life March 2025!

[@gasparcalix2095]

@@fastandsimpledevelopment and I totally agree!

[@duongphuba7216]

@@fastandsimpledevelopment fair enough!! thank you for the feedback, may be you should mention different option to do it with later version java :)

[@alexhu01]

some advice: I have to spend 18/20 minutes to watch you typing all basic spring stuff, and only 2 minutes to talk about modelmapper, which is also very basic.. I'd rather see you go deeper with this library and instead of watching your typing, just put those controller, service files there already and explain them instead..

[@dezee2412]

yes too slow to get focused on ModelMapper

[@mit-zwiebel]

Converter between User and UserDTO should do Controller layer, not Service layer :)

[@MaxxAF]

why should the convert be done in the Controller layer, not Service layer? I'm learning about and I don't know what the best practice is.

[@fastandsimpledevelopment]

I think it is a bit of religion, I like it in the service so all the business type logic is 100% isolated from the Controller and any other part of the application that needs the processing can call it in the Service. If your creating Lambdas you may not have a Rest Controller but still need the Converter / Mapper logic to be used

[@gasparcalix2095]

no! the contoller must be the simplest as possible

[@youssefbouchara1179]

nop, any logic should be out of the controller! The controller is only there to return a response back.

[@johndoedoejohn]

Controller layer needs to get the data and pass it to another layer without any logic involved.

[@cesarbranco1889]

That's work just great. Thank you! Im wondering if you can go deep inside modelMapper and do relationships like @OneToMany, @ManyToMany. Im having some errors using model mapper with relationships. :(