JDBC vs JPA: Pros and Cons

I think this is a great video, but there are some old myths talked about here that frankly remain myths and many just wrong.

#1. Companies are 4 to 5x more likely to change the programmatic front-end UI and app stack then they are the actual backend RDBMS.
#2. far more rare is to decide to change the RDBMS alone.... almost 95% of the time when they are changing the RDBMS they are also changing the entire tech stack (aka company acquistion, merger etc...)
#3. There is more standard cross functionality in the main RDBMS platforms than any front-end UI app stack created to date. If you look at PL/SQL and SQL across the big vendors DB2, Oracle , MySQL, SQL Server vs Postgres. The truth is about 95% of what you need and use most frequently is about 95% the same across all of the vendors. There use to be allot more differences in the 90's and early 2000's but the good thing about RDBMS and the SQL ansi standard is that almost all of these vendors end up landing in the same area when it comes to standards and evolved in the same ways.
#4. Trying to pretend like any of these stacks are going to keep you out of the late night calls on "Forgot to close a cursor"... or a transaction log filled up... or someone did a cartesian product is 100% untrue when on any project of complexity. This is why you either make sure someone on your team has expertise in backend app development or in many situations a DBA can pull double duty to keep this from happening. Matter of fact having good backend knowledge on the team to start with will keep you out of ALL of these problems and make the stack much much simpler.
#5. SQL and PL/SQL are INCREDIBLY easy and they haven't changed much in 30+ years... and they handle things more efficiently inside the RDBMS than any outside language can. And on almost every project and simple and complex CRUD operations can be centrally controlled in one location for tuning, adding additional outside of core app functionality etc.
#6. Many times these days a business database will have more than one interface and centrally locating/abstracting CRUD operations in the database centrally control the logic/behavior and eliminate multiple front-end access points from having variation in they way they say... Create a new customer... create a new contract etc...

Persism is a often better option than those. Check it out.

Great video, thanks for it
also these lights make me feel uncomfortable, natural would work better for me

This video summarizes all the doubts present at the moment of choosing what to use. I've been using JdbcTemplate for a long time and I like it a lot, but right now I am considering using MyBatis just to separate SQL queries into XML files which make java files look cleaner IMHO. Thanks for the great video content 👍

Hey thanks for the explanation. Now i don't have to watch 3 different videos.

In terms of performance like querying millions of records from database, which is faster?spring data jpa or jdbc?

Great video. Thank you. But should I learn JDBC or JPA. I feel like since JPA is more often used than JDBC, I should concentrate on JDBC. Please what do you think?

Love the way you explain things, thank you !

Good explanation. Subscribed 👍🏻

Very good explanation, thank you