i know I am kinda off topic but does anyone know of a good website to stream newly released series online?

@Emery Arturo Try flixzone. Just search on google for it :)

@Trey Brayden yup, I've been watching on Flixzone for since march myself =)

@Trey Brayden Thank you, I went there and it seems to work :D I really appreciate it !

@Emery Arturo Happy to help :D

nice 👍

thx

yeah that strategy sounds reasonable. Because after all time to market is also crucial

am planning to implement the same strategy, thinking of using django for the data computation part then send the results to node...i however don't know if this option will be more expensive than using spring alone

@@marklenet1743 I consider a great benefit in terms of development productivity using node instead of spring if this is a feasible scenario. But if you are already developing stuffs with django then i think you don't even need node and maybe you should stick simply with django

awesome!

@@jgoebel As Alberto suggested to make an external service in SpringBoot to do heavy computation. Is making too many such API calls to a different service a good idea to leverage its computation strength?

good luck for your interview

Exactly 👍

👍👍👍

Glad you liked it!

😁 yeah although I would need to add even though everybody's grandmother can do JS, not many people know it really well. I think the original spec has hundreds of pages

thx

Glad you liked it!

thx UĞUR 👍

Hi Andrew, thx for this comment. Regarding your questions: - with the Node event loop you only have one thread and computations would kill your performance. But Node is very fast at async stuff. Although Spring and Spring Boot kind of upgraded here with Webflux (which is in a very oversimplified way async/await in Java) - I agree. The issue I often encountered that some libraries I wanted to use did not have types. - I find testing with Spring / Spring Boot with Mockito very easy and more flexible. You can even do nice integration test with test containers where you can spin up a docker container with your db and execute all db migrations to see if the changes you did might break something. In JS the "quick and dirty patching" by overriding properties is just very common - tool support for both TS and Spring Boot are pretty good. I see Spring Boot ahead here because Java is so common in the enterprise that there is a tool for pretty much everything. - I see the main advantage of Java / Spring Boot in the nice ecosystem. E.g. ORM support with Hibernate is much better than Node ORMs. The cost of using Spring and Spring Boot is more resource consumption and longer startup times due to component scanning and if the task is only async and no computations, Node might be faster. The big advantage of Java is that there is a nice library for pretty much anything

@@jgoebel Use Micronaut or Quarkus which uses annotation processing to build everthing at compile time. Combine that with GraalVM and native compilation, you have a beast. Also, Netty has multiple event loops (one per thread).

​@@jgoebelI am a beginner and final year Engineering student and I am just not understanding what you guys are talking... Can you please help me choose one frame work to start with to get good job??

my pleasure Gabriel 👍

typically you'd probably only build an API with Node or Spring Boot. And then you would have some SPA (React, Angular, Vue) consume the API. Theoretically you could also do server side rendering with some templating engine with both Node (e.g. Pug) and Java (e.g. Thymeleaf)

thx SriRama

I would pick what you already know and if you want to go into Enterprise applications anyway, I think Spring and Spring Boot is a great choice

@@jgoebel It has been a while actually lol, I came across this video while checking my likes. A lot has happened since then. I started learning JavaScript for during an internship, started learning Node.js and Express, and built a platform from scratch that serves thousands monthly so far, and currently I am working as a Backend SWE using Go (lmao). Who would have thought we will be here? life is crazy.

@@shehabeldinadel8531 nice 👍

I would first make sure you get to a good level in one technology and then move to the next

I haven't looked into it yet, but it looks very promising. Making the containers smaller and having faster startup times is really nice if you use a container orchestration tool like Kubernetes

Spring Boot does come with an embedded Apache Tomcat Server. So you could just compile the code into a jar and run it as an executable but again using a war and deploying it on actual Tomcat Server isn't really hard. You do not have embedded SQL DB at least not the ones you use on production. You shouldn't really be using XAMPP and other tools on production either? Those are more like development tools to be honest. The most difficult thing to consider is learning spring boot is not easy. It is tiring, the official documentation is really bad for a beginner and most of the Stack Overflow solutions may not work for you! I just started learning Spring Boot too and honestly speaking, use ChatGPT! Just use it. It's the only way! Only good way!

I would immediately go with Spring Boot. Initially there was only the Spring framework. But it required a lot of configuration. That's why an opinionated framework on top of the Spring framework was created (that is Spring Boot). Spring Boot sets reasonable defaults for the Spring framework. A lot of things just work out of the box. As you pick up Spring Boot, you are implicitly using Spring. If you did JDBC, maybe you want to take a look at JPA and Hibernate. It is way easier to use than plain SQL with JDBC.

@@jgoebelUnderstood, thank you for your reply Sir . Keep up the good works

what would you like to see beyond CRUD concretely?

@@jgoebel I mean to say, it can be crud but with some extra important features like JWT, conditional redirecting with spring security and JWT. That would be great 💡

@@badripaudel77 thx for the idea. Will add it to my list of potential topics

depends on your needs. If you want to do FE, then React / Angular. If you want to do backend and you already know React, learning Node would be easier.

I think if you are really good at Spring and Spring Boot, you should have a lot of opportunities because this technology is just so common in the enterprise. So imo there is no real pressing need to learn Node for you. I also think that you can ask for higher rates if you do Spring and Spring Boot because it is mainly used in large enterprises that can afford to pay you higher rates. Also I think Spring and Spring Boot is here to stay because there are just so many systems written in it.

Software is a tool that executes on the business model. So you would pick accordingly depending on what domain you are in and what you want to achieve. Both are just tools that provide business value (reduce cost, increase revenue by solving the customers' problems). Both technologies have their place and their usage. Node is clearly easier to get started and easier at the beginning for the software engineers. But once the project reaches a certain size, Node is very hard to maintain in my experience. Spring Boot does a lot better in that regard imo. Spring Boot has a steeper learning curve, but supports pretty much everything out of the box (monitoring, tracing, application performance monitoring) and it has a very rich ecosystem and. Plus if you are doing something with numbers (calculations and so on) and the application is not just primarily I/O, then Spring Boot will do much better imo. However if you just want to get something done as quickly as possible, Node or even Low code tools like Bubble will be much better. Also Node is very good for real time stuff like chats (socket.io). Spring Boot is chosen very frequently in the enterprise and oftentimes the (reasonable) default

Hi Prabhu, that would depend on what you want to do. With express it is very easy to get something up and running quickly and Spring Boot is more suited for larger projects with more sophisticated requirements. In the large companies, Spring Boot is more popular than express

@@jgoebel sir, Can you suggest me five projects to do and that will attract the recruiter.. I'm confusing what framework to learn and what types of projects to do .. plz tell me 5 projects. If I did those projects,then definitely my resume gets selected.I want those types of projects.

thx harambe 👍

very true. It's just about time that these old technologies like Java will be obsolete. Everyone prefers easier and less effortful options so you have to keep up with the new trends.

Java developers has the superiority complex over dynamically typed languages like js,php

@@jackfrost8969 I've been reading things like this for 10 years, people saying that Java is very old, that it is already obsolete, they make me laugh too much. Java is not going to die as it is the most required language in the business sector.

@@Reaper21154 yeah that's the unfortunate truth. Infact even I'm now considering to learn it😂

@@jackfrost8969 Java is like sugar. You know it's bad and you should probably get rid of it.... But everyone loves having it and hence it is still being used 😂

you're welcome man!

You're welcome!

Not really at the moment. Simply because Spring is so dominant in the industry

@@jgoebel it isn't!

@Warrior ts for historical reasons. So Java came out in 1996, C# in 2002. And back in the day Java was really a revolution because it made software development much easier. The thing was also that C# at the very beginning was primarily bound to proprietary Microsoft technology. So they were pushing SQL server and you probably needed to pay licensing fees. That's why the industry went with Java. So even though C# as a language was developing faster (C# had Lambdas way earlier than Java), the industry sticked with Java. Later on the C# ecosystem openend up especially with .NET Core but by then there was already a huge amount of software written in Java. And since C# does not provide substantial advantages, the industry sticks with Java until today

you're welcome valluri 👍

If you are willing to deal with extra long error messages that are hard to read

@@FeLiNe418 it is annoying that there are always some flaws in programming languages don't u think? Humans are flawed.

I think with Spring Boot you have better chances because it is so common in the industry - especially in large companies. Large companies typically pay better and have better benefits. Ideally though you can do both

@@jgoebel thanks ❤️

yes, NestJS in general leads to better project structures in my experience and just like Spring Boot, it uses dependency injection. I personally prefer Spring Boot for the enterprise because Spring Boot and friends have support from pretty much anything out of the box (table auding with Hibernate, database migrations, Java provides multi thread support).

I've put it on my list of potential topics 👍

thanks man, I appreciate that 👍

thx jos 👍

Not sure if I understand what you mean. You could use Node and Spring Boot in the same cluster (e.g. in a Kubernetes cluster with multiple microservices).

Yes, you can, and communicate between whatever part of the project you build with the other language as a microservice.

You can build microservices in whatever language you want, and communicate via REST API.

Hi Darsh, I would say Spring Boot. So both Spring Boot and .NET Core are used in the enterprise. However .NET Core is relatively new and that's why Spring Boot is more widespread. Node.js is not so common in big companies because it is hard to fulfill all the security and compliance guidelines and it might be hard to write complex business logic with it (e.g. building an accounting system for example)

@@jgoebel in your Opinion I Choose Node js or Spring BooT And i want to get a Big Job in Big Company ???

@@darshmostafa6044 Hi Darsh, I would go with Spring Boot because it is very common in the enterprise

Spring Boot is very common in the enterprise sector and there are a lot.of jobs for it. So if you're proficient in it, I think there should not be any issues.

@@jgoebel thanks i am improving and polishing my skills daily thanks

@@aqibishaq885 how u doing so far bro

I mean doing computations, calculations. Anything you would need in a business environment e.g. building an accounting system or storing transactions

Hi Ishan, now you can do both. That's great 👍

if you are new go for MERN, there is much more information online since it is trending right now.

MERN is probably easier to get started with. Dealing with relational databases is way easier in Spring Boot than with Node thanks to Hibernate

In my experience, it is easier to get started with JS and get something small to work, but it's quite hard to maintain a large code base properly and run a larger JS project in prod in a stable way. I think maintaining a larger code base is a little bit easier with Spring and Spring Boot because it is opinionated and static typing also helps (although TS can help here, too). In addition Spring supports pretty much everything out of the box and if not there is a high quality third party library (feature flags, metrics, application performance monitoring, table auditing, high quality ORMs). It is mostly just a matter of configuration with Spring Boot

@@jgoebel for me it is much easier to code in Java because of the tooling available. But there cases you need to use JS like frontend or multi platform mobile development like RN or single skill set for frontend and backend (node). JS is an odd language, it has things not present in other procedural and/or OOP languages. After experiencing JS for 3 years I will say JS is harder than other languages and Java in most cases much easier. Those who say JS is easier are either have not developed non-trivial system in JS or does not know JS in detail. Also, the way I see it there are less available capable JS devs than capable Java devs.

Difficulty is subjective. Just because you find JS harder, doesn't mean others should too. And it's a fact that most people find it easier.@@rommellagera8543

😁

Yes, Typescript would mitigate the typing issue. But there's more in my opinion: Spring Boot with Hibernate supports pretty much everything out of the box (e.g. auditing database tables and so on). You would need to build something custom for that I guess in Typescript. Plus with Typescript you are still only single threaded

only in winter 😁