So You Want to Build An Event Driven System? - James Eastham - NDC Oslo 2024

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

КОМЕНТАРІ • 16

  • @aiiaznsk8er
    @aiiaznsk8er 3 місяці тому +2

    the analogy of strong vs eventual consistency when paying with cash versus credit is really good. I'm totally going to be using it from now on.

  • @unexpectedkAs
    @unexpectedkAs 3 місяці тому +2

    Very good introduction! Id love a part 2 that delves into the event bus topology, sagas, idempotent events, error handling, etc.

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

    When talking about event driven and CQRS, I see it like this: Command events implement the "C" of CQRS, and ECST replaces the "Q" of CQRS.

  • @JamesLee-ge4wu
    @JamesLee-ge4wu 4 місяці тому +1

    Thank you for the great presentation. One of the challenges that I often face is: how do you deal with past events that didn't have the chance to be published because we introduced event-driven system much later?

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

    Does people really implement application this way ? How's the quality of life of those people ? I'm skeptic.

    • @black-snow
      @black-snow 3 місяці тому

      Yup. QoL is great but perhaps not where you think it is. Is it fast, resilient, scalable ...? Yeah, sure. I think the greatest effect, though, is that you talk about the business again. Especially when you face a world where everything is CRUD it's such a relief.

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

      @@black-snow Business people discussing in imperative event-driven logics ? I'm still skeptic.

    • @black-snow
      @black-snow 3 місяці тому

      @@sakesun What are "business people" to you? Shouldn't everyone working in a business be "business people"?
      It's about speaking the same language. It just plays so nicely with DDD. Dev teams are often so far away from the actual problem we're supposed to solve that we don't even understand the lingo of our users.

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

      @@black-snow And "the language" to solve business problem is imperative event-driven logic ? I'm still skeptic. Can anybody else please help confirm this kind of environment is actually exists in real world.

    • @black-snow
      @black-snow 3 місяці тому

      @@sakesun why imperative? You may have commands, sure, but if it's _event_-driven I wouldn't call it imperative. Things happen and other things react to that causing a graph of reactions.

  • @BrianGentles
    @BrianGentles 4 місяці тому +3

    It's not a "depreciation" date! The words is "deprecation"!

    • @baka_baca
      @baka_baca 3 місяці тому +2

      Sometimes a difference in word choice can just be a difference in culture, your comment doesn't help I'm afraid. Also, I see you've made a language error yourself in your comment.
      Relax a little, this was a really good talk, there's no need to take offense to using a different word in this case, there's no misunderstanding because of it.

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

      @@baka_baca depreciation and deprecation are very similar words with similar but distinctly different meanings - it makes sense to distinguish the two. doesn't diminish the excellent talk to do so!