المدة الزمنية 22:33
.NET Developer tries Java Spring
تم نشره في 2022/12/30
.NET developer tries the Java Spring framework. Looking at the daily life of a Java developer & some beans. Patreon 🤝 https://www.patreon.com/raw_coding Courses 📚 https://learning.raw-coding.dev Shop 🛒 https://shop.raw-coding.dev Discord 💬 https://discord.gg/xgNS26k Twitter 📣 https://twitter.com/anton_t0shik Twitch 🎥 https://www.twitch.tv/raw_coding 👉 Try Rider https://www.jetbrains.com/store/redeem/ RD5K9-4TXXW-KMV3G-NYWSF-3ZSTP #aspnetcore #spring #java
الفئة
عرض المزيد
مقاطع الفيديو ذات الصلة على .NET Developer tries Java Spring:
same bro, same 658
;-) 6
JPA stands for Java Persistence Api, which should tell you what it's for. :)
Now you can use spring boot which comes as part of code that performs basic configuration at runtime 2
Could you do a similar video on NestJS? 1
I do agree on the security part, it seems a bit hard, sometimes like "whack a mole"
But
For complex queries we use JPA Specification which allows you to create queries easy to maintain and modify.
I would agree on the fact that it has somewhat large learning curve, especially if you spend a day on it, but after some time, things do become a lot better :D
Thx for the video
And I guess, authentication is always a mess :D will you try ktor to compare it to spring?
What’s the plan for 23? 2
maybe we can extend this to frameworks as well ;)
- I don't think these magic queries will be suitable for complex real scenarios.
- I like
- many to many is much cleaner in EFCore.
- The Generics in java is just converting to objects under the hood, the language design is worse than C#.
Everything is easy to configure and conventions are easy.
Anything can
I am proud to be a Java Spring Boot developer. It's breeze to do development with Spring!
First off, Spring Security is so bad they decided to
Secondly, Beans are actually just singletons and are left over from the OG Spring. In Spring Boot they are mainly used for small configuration setups where you have some class that exists and you can't alter to make it a component/service/controller or whatever else, so you define it as a bean so that you can do DI with it. How it works with Spring Boot is that you create a class, and then specify whether it's a @Service, @Component, @Configuration, etc. (something like in .NET Core, but instead of having a separate config/Program file you'd do it on the class itself with an annotation).
And finally a rant on JPA. It's fantastic and magical and that's the main reason I'm still sticking with Spring rather than .NET, I can't stand the EF Core, but Many-To-Many relations are SO BAD it's unbelievable. General rule of thumb in Spring developer circle is try to avoid implementing those relations, and if you have to, create an intermediary entity that will have 2 one-to-many relations and then try to avoid fetching them as much as possible. For custom queries we have a ton of different possibilities like QueryDSL, JPAQuery, @Query and a whole slew of other options, so it isn't painful in the slightest (only thing I'd maybe call painful is transaction management since it does TOO MUCH magic).
Sorry for the rant, and thanks for coming to my Ted Talk.
If you simply add the spring security dependency to the
Adding users, user details services, roles, and authorities is more involved though.
Also the method you wrote to find a student by id, was actually already defined for you because it's part of the JpaRepository you extended.
JpaRepository has a bunch of predefined methods you can use including save, saveAll, findById, delete, deleteById etc.
Also, you can abstract more boilerplate code with tools such as Lombok, which will take care of all your getters, setters, constructors and tons more, and also JpaBuddy that will help create and configure your entity classes and repositories etc.
I think with a little more context is worthy of a second opinion don't you?
You can define a lot of simple queries by simply adding a method to the interface like "findByUsername(String
And yes, "findByUsernameAndZipcodeAndFavoritecolor(String username, int zipcode, MyOwnColorType favoritecolor);" will work as well.
The automatic migrations are where it gets difficult - because it doesn't automagically catch ALL things it should migrate.
E.g. you have a field mapped to a varchar(30) and want that to be a varchar(50) - it won't migrate automatically and you'll end up writing your own migration scripts again.
Dude doesn't know what dependency injection is?
He
The project has no structure, bestie just copied/pasted code with some minor changes and thinks it'll work as expected. That's what I did in my first year
Bro didn't know what a Bean is. Did he google it? Nah, why should he?
ORM : Steve Jobs's WebObjects which
Component : Again WebObjects has it some 30 years ago. At first I was so puzzled/confused of why the need of all these server side JavaScript frameworks React, Angular, NodeJs??? After diving in to investigate, my immediately feeling was WTF. After 30 years these web frameworks still don't have its own DOM and therefore must rely on NodeJs which came from Chrome and then React, Angular to run on NodeJs. All these frontend/backend different languages, tools.I'm speechless. Until DotNetCore Blazor, my goodness finally.
It really depends on the complexity of your project. Just to display certain dynamic info or a simple HTML form PHP, JSP is fine. And then Spring, Jango has MVC. Template system make reusable HTML possible. DotNetCore Razor page MVVM is better than MVC because once your project grow, it will be hard to keep track of which controller to which view. And stateful component Blazor is a totally different class. Once matured, third party vendors like Mud, Syncfusion, Telerik can make developing complex UI real easy.
After trying .NET 5, I never went back.
I don't understand
Thank you for this video!
how you did it in 20 minutes
@AutoWired to indicate injections;
@Bean to indicate wherever that can be Injected; WTF 1