Keynote: Introducing Spring Framework 6

Поділитися
Вставка
  • Опубліковано 18 гру 2024

КОМЕНТАРІ • 37

  • @falconheavy595
    @falconheavy595 Рік тому +15

    It's always a great feeling to get a Spring lecture from Brad Pitt

  • @Anbu_Sampath
    @Anbu_Sampath 2 роки тому +14

    Nice advice - keep your JDK/EE/Spring Framework keep upto date. World is moving faster.

  • @danielmichalski2436
    @danielmichalski2436 Рік тому

    Great explanation of virtual threads

  • @europeantechie
    @europeantechie 2 роки тому +10

    Virtual threads is a game changer for reactive. The pitfalls of reactive in combination with legacy database drivers is crazy and cannot be argued for now that you can do the same - honestly, even a lot more performant because resource access is actually handled non-blocking - by 'just a few lines of code in a configuration file'. All of a sudden, I can again hire every Java engineer and nobody needs to build complex reactive queries combining multiple data streams that in the end - guess what - are blocking anyway because R2DBC doesn't support relations for relational databases so we we use blocking calls for any database access and lose all the theoretical gains.
    Everything else is really nice but this is the best feature for me personally.

    • @adambickford8720
      @adambickford8720 2 роки тому +2

      You're conflating a bunch of ideas here; you have no idea why you're upset.

    • @europeantechie
      @europeantechie 2 роки тому +1

      @@adambickford8720 I thought I was very precise, feel free to point out inconsitencies - but be more precise when you do so.

    • @adambickford8720
      @adambickford8720 2 роки тому +2

      @@europeantechie " are blocking anyway because R2DBC doesn't support relations for relational databases"
      You're conflating the threading I/O model with ORM behavior. You then conclude something that is provably false.
      R2DBC 'understands relations' just as well as JDBC does. If you need joins and projections... write them. If you want a reactive alternative to JPA, Hibernate has a reactive offering.
      If you insist on misusing R2DBC and zip() together a bunch of async results sets, there is STILL no blocking. Thats... the entire point. Its still a dumb idea but at least you're not wasting threads to fail.

    • @europeantechie
      @europeantechie 2 роки тому

      @@adambickford8720 that is actually a good starting point to dig deeper, thanks for taking the time

  • @sujitjoshi1240
    @sujitjoshi1240 Рік тому +1

    I’m so glad to see his face. His name is ALL over Spring code.

  • @hellojj5
    @hellojj5 2 роки тому

    Thanks for the good information

  • @THE16THPHANTOM
    @THE16THPHANTOM 2 роки тому +1

    so is there a reason they are moving at the is speed? why didn't they move as fast before? also does this mean those certification exams and the people who make them are FAQ'd, since it takes way longer to make those?

  • @chandragie
    @chandragie 2 роки тому

    AOT (Ahead-Of-Time) and Virtual Threads are interesting!

  • @bitabhinav1
    @bitabhinav1 Рік тому

    is there a place from where I can download these slides??

  • @meteor8076
    @meteor8076 2 роки тому

    Thanks!

  • @arghyamitra3281
    @arghyamitra3281 2 роки тому

    💌 spring , but I think Amazon Lamda SnapStart is based on project Crac

  • @iamNirbhaymishra
    @iamNirbhaymishra 3 місяці тому

    Brad Pitt giving walk through , I want Tom Cruise also :)

  • @incongnito12
    @incongnito12 2 роки тому +2

    and here i am struggling with spring 5

  • @zoladkow
    @zoladkow 2 роки тому

    WoW is 18 years old too 😁

  • @ocleidyreve6361
    @ocleidyreve6361 2 роки тому +13

    So, they will continue wasting time with webflux after virtual thread GA....Good luck

    • @57skies
      @57skies 2 роки тому

      so you think that webflux is going to be based in something different when loom is production ready? You seems to miss-understand things

    • @ocleidyreve6361
      @ocleidyreve6361 2 роки тому +5

      ​@@57skies What part of my small comment suggests something like that??.
      It doesn't matter if webflux use netty or virtual threads.
      The simple idea of maintaining another ecosystem in parallel for very few benefits and serious problems is just insane.
      Only time will tell. Good luck

    • @loooke7197
      @loooke7197 2 роки тому

      @@ocleidyreve6361 just for my understanding, are u saying webflux has only few benefits and serious problems ? (I'm new to spring boot)

    • @ocleidyreve6361
      @ocleidyreve6361 2 роки тому +2

      ​@@loooke7197 In my opinion, if the code is difficult to debug, with useless stack trace, poor readability, poor interaction with platform tools, and also aims to fork every library in the ecosystem that touches IO, then yes, it has serious problems and this is not only specific to java, but at least we have a friendly alternative (virtual threads) in front of us.

    • @loooke7197
      @loooke7197 2 роки тому +1

      @@ocleidyreve6361 Thanks. Yeah, i hated working with Weflux also. I recently created an API that used WebClient library. So I had to make the whole API reactive since webclient is reactive. It was such a headache.

  • @asankaishara
    @asankaishara 2 роки тому

    interesting. thanks

  • @razatech22
    @razatech22 5 місяців тому

    Video quality reduced to 360p

  • @saga3273
    @saga3273 2 роки тому +11

    Tel Aviv, Palestine is absolutely stunning ....

  • @pstha4537
    @pstha4537 Рік тому

    Make Spring boot more minimalist. it is too verbose.

  • @_oo.monkeypox.oo_3344
    @_oo.monkeypox.oo_3344 2 роки тому +1

    First

  • @맥진-w1p
    @맥진-w1p 2 роки тому

    Third

  • @kyuseokchoi8757
    @kyuseokchoi8757 2 роки тому

    second

  • @rnz2363
    @rnz2363 2 роки тому +1

    terrible framework