Also I think docker must be bundled in testcontainers because, as I understand, the intention of testcontainers is to use the containers in integration tests and not always CI/CD environments will have Docker available out of the box
Will dev mode restarts be still be fast in case of large applications (that have some some hundreds of entities, also some schedulers configured and bunch of external integrations)?
Hi.. im quiet new and i would like to know what the benefits of the constructor injections are. I could not find a good answer jet, why i should use it.
hello, thanks for watching the episode. the main benefit is that its easier to see what the type requires to be in a valid state. also, you won't need Spring or any framework to test the component.
@@coffeesoftware not to mention if you use Lombok and its RequiredArgsConstructor, you don't even need to declare the constructor manually, just make sure your injected items are declared final, and Lombok will do the right thing. Handy when you have more than a few details to inject. Never fun when the constructor requires more than 3 or 4 parameters (though in all honesty that's probably a code smell and reason to rethink the design of the class).
I hope spring team understands that current dev mode is not attractive. Quarkus dev is a real dev mode. All those things with recompile looks like manual tedious process in the pure automated pipeline.
Love the springboot demo and seeing test containers and native image support.
What is meaning of native image support?
@@arnabchowdhury4892 I think he is referring to the "GraalVM Native Support"
Also I think docker must be bundled in testcontainers because, as I understand, the intention of testcontainers is to use the containers in integration tests and not always CI/CD environments will have Docker available out of the box
Condensed and nicely paced video. Thanks for sharing! looking forward to SB 3.1 ;-). Keep up the good work.
Will dev mode restarts be still be fast in case of large applications (that have some some hundreds of entities, also some schedulers configured and bunch of external integrations)?
For the testcontainers part, why don't create a profile like for instance a dev profile and create the testcontainers configuration with this profile?
Please make a project with spring security and JWT in spring boot 3.1.0
docker-compose now support hot reload of changes
which theme are you using in intellij please?
springboot 3.1 not compatible with eureka discovery server any compatible alternative?
Not sure if it has what you need, but a compatible release of Spring cloud is planned for next week.
@@JamesStansell okay thanks alot
Native image support is nice..🎉
Started DemoApplication in 3.71 seconds on MBP-M1 Pro, 15x slower than on movie :)
LOVE IT
This is just awesome
Hi.. im quiet new and i would like to know what the benefits of the constructor injections are. I could not find a good answer jet, why i should use it.
Google is willing to support you.
Don't be lazy!
hello, thanks for watching the episode. the main benefit is that its easier to see what the type requires to be in a valid state. also, you won't need Spring or any framework to test the component.
@@coffeesoftware not to mention if you use Lombok and its RequiredArgsConstructor, you don't even need to declare the constructor manually, just make sure your injected items are declared final, and Lombok will do the right thing. Handy when you have more than a few details to inject. Never fun when the constructor requires more than 3 or 4 parameters (though in all honesty that's probably a code smell and reason to rethink the design of the class).
WTF ? Authorization Server, didn't Spring just depricate their own OAuth2 server year or two ago in favor of sunign Keyclock ?
save keyboard please
🤯
This guy is on steroids 😆
I hope spring team understands that current dev mode is not attractive. Quarkus dev is a real dev mode. All those things with recompile looks like manual tedious process in the pure automated pipeline.
noice
using record classes for entities is not a good practice.
You find out what *does* work with hibernate, not what *doesn't*. In general, hibernate = "this is why we can't have nice things".
Why not? Just for my info
@@fruitsalad1255records are immutable.
good for a quick demo, no? man didn't even use lombok lol.
I wonder how it works without entity annotation