Hi! It would be nice to see how I could be productive writing tests and developing quarkus since I don't use a browser when I'm writing code :) the second thing is that spring has integrations for almost everything (Kafka, azure stuff, etc etc.) and nice configuration support. Will I miss it using quarkus?
Well, spring with spring native can come a lot closer to this level of performance and hides graalvm complexities. Spring is definitely not the ideal candidate for FaaS application, but for a standard microservice which does not need to start up cold too often, spring ecosystem provides a lot more feature value and it is also reactive first with spring boot 3, therefore can gain a lot more juice from the compute.. I hope spring native/micronaut concepts pickup similar traction to this.. Like to learn more abt memory footprint comparison mentioned here and see the difference.
What is your point? The presentation demonstrated how it can speed up development time and startup time and how you can lower a spring application's server footprint with minimal changes compared to spring boot coding. And no it's not the same spring it's an exceptional spring presentation using quarkus
@@zedisdeadz See the history of Quarkus. It was started development with Java EE. But Spring is monopolly and not the Java EE because Spring has its own API which has nothing to do with Java EE. So the Spring in Quarkus is a hack as the whole Spring is hack.
@@georgiosandrianakis8636 Spring has its own API. It is not Java EE API. If you understand the history and what the Spring guys did in JCP, you would see that they wanted to track JCP activities and manage their business in advance. But it was not always Java EE API they released. See for instance the REST annotations in Spring and EE. They are not identical and not certified by JCP and Jakarta EE either. It was a pure business making in Spring Source which caused monopolly in the world by the Spring. On the other side Java EE or Jakarta EE is not monopolly because the API has aplenty of implementations. Spring is only one. And that's the significant difference.
@@zedisdeadz Quarkus is Java EE. But spring is a kind of glue unnecessary. The pripamy API focus in the Quarkus was of course the Java EE API and not the Spring. People with many experiences know that Java EE did produce also very small JAR Uber file and footprint. It is all about the technical overview on the globe.
![Kubernetes Crash Course for Absolute Beginners [NEW]](/img/1.gif)
Thank you for the presentation! That was awesome!!! :)
Amazing presentation with live coding! Thank you George!
Thank you for the nice presentation, love Quarkus !
Pivotal: Spring Graal Native
Red Hat: Spring apps on Quarkus
Hi! It would be nice to see how I could be productive writing tests and developing quarkus since I don't use a browser when I'm writing code :) the second thing is that spring has integrations for almost everything (Kafka, azure stuff, etc etc.) and nice configuration support. Will I miss it using quarkus?
Well, spring with spring native can come a lot closer to this level of performance and hides graalvm complexities. Spring is definitely not the ideal candidate for FaaS application, but for a standard microservice which does not need to start up cold too often, spring ecosystem provides a lot more feature value and it is also reactive first with spring boot 3, therefore can gain a lot more juice from the compute.. I hope spring native/micronaut concepts pickup similar traction to this..
Like to learn more abt memory footprint comparison mentioned here and see the difference.
Amazing !
😍👍
Still the same Spring hacking into EE. What about Deltaspike Data instead of Spring Data.
What is your point? The presentation demonstrated how it can speed up development time and startup time and how you can lower a spring application's server footprint with minimal changes compared to spring boot coding. And no it's not the same spring it's an exceptional spring presentation using quarkus
@@zedisdeadz See the history of Quarkus. It was started development with Java EE. But Spring is monopolly and not the Java EE because Spring has its own API which has nothing to do with Java EE. So the Spring in Quarkus is a hack as the whole Spring is hack.
@@tibordigana2551 I don't see how you come to this conclusion
@@georgiosandrianakis8636 Spring has its own API. It is not Java EE API. If you understand the history and what the Spring guys did in JCP, you would see that they wanted to track JCP activities and manage their business in advance. But it was not always Java EE API they released. See for instance the REST annotations in Spring and EE. They are not identical and not certified by JCP and Jakarta EE either. It was a pure business making in Spring Source which caused monopolly in the world by the Spring. On the other side Java EE or Jakarta EE is not monopolly because the API has aplenty of implementations. Spring is only one. And that's the significant difference.
@@zedisdeadz Quarkus is Java EE. But spring is a kind of glue unnecessary. The pripamy API focus in the Quarkus was of course the Java EE API and not the Spring. People with many experiences know that Java EE did produce also very small JAR Uber file and footprint. It is all about the technical overview on the globe.