Spring Boot 3.2's Secret Weapon: Auto-Configured JDBC Client for Effortless Database Integration!
Vložit
- čas přidán 10. 09. 2023
- Welcome to the future of database integration with Spring Boot! The latest release, Spring Boot 3.2, brings forth a powerful new feature that's set to redefine how we interact with databases: the Auto-Configured JDBC Client. Gone are the days of tedious configurations and lengthy setup processes.
With this secret weapon in your arsenal, you can now effortlessly connect, read, and persist data to your database, all within the familiar Spring ecosystem. Whether you're a seasoned developer or just starting out, this JDBC Client promises a streamlined experience, ensuring your projects are not only efficient but also scalable.
🔗Resources & Links mentioned in this video:
GitHub Repo: github.com/danvega/jdbc-client
Rest Client: www.danvega.dev/blog/2023/09/...
👋🏻Connect with me:
Website: www.danvega.dev
Twitter: / therealdanvega
Github: github.com/danvega
LinkedIn: / danvega
Newsletter: www.danvega.dev/newsletter
SUBSCRIBE TO MY CHANNEL: bit.ly/2re4GH0 ❤️ - Věda a technologie
This is the amount of abstraction I was hoping spring would provide for JDBC. Glad it made the cut!
nice! 3.2 is going to be such a cool release!
Dan, See you reppin' the Browns! Nice dub yesterday! Thank you for your content, love all your videos!
Thank you! Great tutorial! Awesome channel! 💛
Thank you!
Nice topic thanks !
Fantastic!
In our project, we have an internal library for working with JDBC that provides wrappers around jdbcTemplate, like `tryOne()`, `update()`, `list()`, etc. I think, once Spring Boot 3.2 is released, I will replace our custom code with Spring Boot built-in support. There will be less code to maintain and understand!
Thanks for the video, Dan!
Great topic. It seems to be pretty clean. Hopefully the mappings work out as aspected (because jdbcTemplate rowMappers were strange for some null fields :) )
Just grate!
It's really awesome to have fluent DSL clients instead of classes bloated by overloaded methods.
I was really waiting for RestTemplate replacement and finally it happened (hopefully it will be deprecated and removed soon).
With JdbcClient I would probably go further - to extend with select/create/delete/update - to make similar to JOOQ API.
Pretty neat. Almost feels like Jooq ;)
Hey Dan, Can you do a video on Spring Modulith project?
You don't need the Qualifer annotation if you name your parameter just like your class. Spring boot will find out automatically which implementation of the interface you're asking for
What about getting generated keys? The KeyHolder in JdbcTemplate was weird. Even weirder in the DatabaseClient in r2dbc
Wondering if this might be useful with a database that is set up to be accessed issuing stored procedures? Switching the legacy access to jdbc template and row mappers was prohibitive.
@Dan Vega what if in the select clause we have a column named f_name and in the java class it is defined as firstName how can we map column to properties?
Could you elaborate on the difference between spring-data-jdbc and JDBC client? Which one do you recommend?
Hi Dan,how to use PreparedStatement in three JDBC Client or it internally uses it?Thank you in advance
20:21 how do you get such nice json formatting? Is it some chrome extension?
JSON formatter for chrome
what buttons are you using to get post-schema etc. templates in intellij
which plugin you have used for templates
Is there a difference between a service and a repository.
I've seen in some tutorials you use @repository and in others @service.
What is the difference? When to use which?
How does it handle mapping enums on the record?
Just wondering, why would anyone choose JDBC template or the new JDBC client over Spring Data JPA?
Are there any use cases where JDBC template or the new JDBC client would be more useful or preferable than Spring Data JPA?
@@sagarbhat1 I have such a case. I have a spring boot app that needs to connect to IBM's Netezza Data warehouse. Netezza has its own jdbc driver and since Hibernate or spring data JPA do not support Netezza. I'm currently looking for an alternative approach (i.e. better than the raw jdbc one).
Doesn't Quarkus already have such a (or similar) feature?
dan, can you make an introductory video on spring boot 3.0 for noobs?
I certainly can... What would you like the video to be focused on? What's new in Spring? What are you trying to build with it?
thanks great videos, I only suggest a litte more zoom in the videos if you can. Have a god day
Zoom on the code?
@@DanVega yes thanks :)
It is pretty visible, and much better this way if you ask me as we see more code and if the quality of the video is fine, there are no issues with reading.
the question is why i use jdbc even jdbc template when i have JPA????????
The more question marks you add, the better the question is
@@diegoshevek5927 it's beyond my mind. would you like to tell me the answer in appropriate topic ?
Why would you do that instead of using JPA?
If you are working on an old codebase with raw jdbc ResultSet. The migration will be smoother, the team will avoid shooting itself in the foot with JPA/Hibernate, and the performance will be preserved.
@@ocleidyreve6361 yes with an old codebase you have a lot to do, but i am wondering for new projects, it does not make a sense
🤤 "Promosm"