Видео

This should have more views

Top🎉

10:30 what a great insight!

After reading through tons of content and going through multiple videos , finally I found what exactly I was looking for. Great presentation with precise reasoning and content. Thanks!

The way term upstream and downstream being used here is confusing. I hope it varies based in the flow of request and response.

Nice video sir

Nice video

Nice presentation, thank you folks! 👍

Great talk, addressing the main points to consider when Architecting for Data-Intensive Workloads

Hope they can release strong templates with syntax similar to JavaScript. The factory approach looks more verbose

Very nice presentation with a real example 👏👏👏

As usual, a great talk.

At 33:00 booleanLock is used for the whole library while synchronized(book) is used for that specific book only, right?

Thx

Opa... mande aí o vídeo sobre Spring

It's always nice to see the sneak peaks, and FFM really is a magnificent enhancement.

MP Metrics is in a wierd state. some implementations have ditched in for micrometer. not sure whats going on there.

"I know that Spring people do not love to write Java code so much, Spring people love to write their code more in terms of annotations" - incredible line.

Thank you so much for this wonderful presentation! Your explanations on CQRS and modern Java were truly enlightening. The way you tackled complex topics in such a clear and simple manner increased my interest even more. Great job, and much appreciated!

Tools are not a very good idea in the case of the sending email feature because it becomes like magic and not easy to understand how it works for a developer.

Spring AOT wäre der bessere Vergleich gewesen.

Great video! I was a simple but quite straightforward explanation. This helped me to get an introduction to LLMs and how we can use it to build applications. Thanks for sharing Elder & Java Pro!

Worth to watch this video and learn. Great presenters + presentation and shared many insights into build/runtime/startup performance improvements and strategies.

Nice. But I will deploy OTel in Kubernetes and hook it with an endpoint. No need to burden the Spring boot app.

A great presentation on what's to come in Jakarta EE 11!

Great talk

Amazing. Have you shared your code in github ?

Would love to take a look at the Github repo for this.

This is a brilliant talk and it has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats Nicolas👏

This is a fantastic talk and it has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats Abdel!

Amazing! thank you but is there any way to get the code available on GitHub?

Thanks for a great talk. Will definitely checkout helidon

Hi Balkrishna, Thank you the amazing informative video. Would it be also possible to monitor that a virtual thread was unmounted from a platform thread and that platform thread was used by another virtual thread

Informative

01:30 ArchUnit 03:50 awaitility 05:44 jacoco-agent 08:55 pitest 12:16 TestContainers 13:41 gatling + jmc (jmeter alt) 19:10 equals verifier 20:16 handlebars 22:36 javapoet(generate dynamic classes) 24:09 jobRunr 25:54 jsoup 26:42 libPhoneNumber 28:17 timefold(scheduling) 33:12 apache spark 36:20 togglz 38:54 owasp-dependency-check 40:13 passay(Dynamic Rules) 42:00 dependabot/renovate 42:46 openrewrite 45:24 maven daemon(mvnd)

Very interesting. Thank you

Volume is too low

The audio volume for this one seems quite low, an interesting talk though.

Thanks

Super Vortrag 😊

Actors are NOT Objects. There are many differences. First Objects are called synchronous, actors not. Objects are passiv, actors not. Objects are multi-threaded, actors not.

Very thanks, but sound quality is so bad that I can't hear anything clearly.

Der Talk ist auch für Docker Einsteiger interessant!

Very interesting talk. Thanks.

Thank you so much for this wonderful opportunity. 🙏🏾

Why Eclipse Serializer? Why do avro, protobuf ... not work?

Kotlin ist seit April der Default für neue Gradle-Projekte und bietet jede Menge Vorteile. Gibt es einen Grund, wieso Du trotzdem Groovy nutzt?

Totally worth it