Introduction to Project CRaC: Enhancing Runtime Efficiency in Java & Spring Development
HTML-код
- Опубликовано: 17 июн 2024
- This video provides an introduction to Project CRaC and its role in enhancing runtime efficiency in Java and Spring development. It explores the challenges faced by developers in optimizing runtime efficiency and how Project CRaC addresses these challenges. The video covers key concepts and techniques used in Project CRaC, highlighting its benefits and potential impact on Java and Spring applications. Whether you are new to Project CRaC or looking to deepen your understanding, this video is a great starting point for developers interested in improving runtime efficiency in their projects.
🔗Resources & Links mentioned in this video:
Azul Documentation: docs.azul.com/core/crac/crac-...
Spring Boot 3.2 + CRac: foojay.io/today/springboot-3-...
Spring PetClinic: github.com/spring-projects/sp...
Building a Container: github.com/sdeleuze/spring-bo...
👋🏻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 ❤️ 
Наука
Thanks for the video! Definitely will be following this closely. Glad spring is picking up on this, I heard about Crac 6-12 months ago and was pretty stoked about it. It would be nice to have a concrete example of how not to store sensitive data/secrets in the snapshot vs how to do it properly though since even as a seasoned veteran around security, I still don't understand how to do it securely when it comes to these "snapshots".
Would love to see a tutorial on using Spring Cloud Sleuth (its replacement, technically) & the ELK stack in Spring Boot 3!
Or Kafka messaging in SB 3!
I struggled learning these two things for my SB 3.1 project so much that I downgraded to SB 2.2 😅
Oh no! Not even 2.7? What issues did you run into?
I have said this before. I am fascinated with this project. Thanks for the video! I don’t think I’ll be using this anytime soon in production because I don’t have these requirements, but I do want to keep up to date with the developments surrounding project C.R.a.C.! Hopefully giving you feedback soon!
Thank you and we are glad you enjoyed the video.
Hello can you cover new virtual threads support in spring boot 3.2 since they are officially supported
yes S.B 3 support virtual threads
Are there benefits in terms of startup time if some changes are made for application coding and the restart. Can CRaC be considered for bringing DEV mode of application starts?
Just a small correction it started in 408ms, and not 40 as you said at @27:10 which deviates a lot from the slide @09:27. Why is that?
qq, is junit 4 is discontinue in spring boot 3? Thank you very much. sorry, it is not related to CRaC.
JUnit 5 has been the default for a little while now. You should be able to include the right dependencies and versions and use it still.
Thank you very very much.@@DanVega
could you also make a video of CRaC with a tutorial starting from scratch?
I'm not sure what you mean from scratch? There isn't anything specific from the code we wrote, it's more of a build time feature when we move to production.
♥
Looks good. Not very useful for most projects though - and also setup looks harder. I think when it gets easier to setup it will be used more widely
The be honest. As a java and spring profesional. The monent that I recoggnoze that I need faster boot times or less memory footprint, that moment is to lookup for an other languge like go or rust for example. ( I don't know how kotlin behaves ). The nefit o java is the JIT for long running tasks. It generates the optimized code for that current processor. And that is unbeatable for long runnung high performant tasks. I don't know if that investigation make sense or not.
Spring has a native image project, I think you should give preference to it if you use Spring
the problem starts with dependencies that are not directly from spring, its not there yet, a lot of dependencies are not supported yet
Read a bit about GraalVM - Native (AOT) vs. ordinary JVM with JIT. One problem of AOT is, code is not optimised which leads to less throughput ;)