Messaging: The fine line between awesome and awful - Laila Bougria - NDC Oslo 2024

Поделиться
HTML-код
  • Опубликовано: 12 сен 2024
  • Messaging: The fine line between awesome and awful (and how to stay on the right side of it) -
    This talk was recorded at NDC Oslo in Oslo, Norway. #ndcoslo #ndcconferences #developer #softwaredeveloper
    Attend the next NDC conference near you:
    ndcconferences...
    ndcoslo.com/
    Subscribe to our RUclips channel and learn every day:
    / ‪@NDC‬
    Follow our Social Media!
    / ndcconferences
    / ndc_conferences
    / ndc_conferences
    #architecture #microservices #messaging
    Distributed systems are becoming increasingly common in today's systems landscape, and messaging is often used to coordinate between components in these systems safely. With benefits like increased reliability, better performance, easy scalability, and easier decoupling of components, you might quickly think, "Shut up and take my money!". However, as with any architectural choice, the other side of the coin surfaces challenges and pitfalls that we must consider: structuring code to fully leverage messaging, dealing with duplicate messages, ordering issues, and diagnosing problems.
    To tackle these challenges, we'll explore different messaging communication patterns and when to use them, learn how to effectively decouple code and consider techniques for system consitency. We'll also prepare for any unexpected issues, because, Murphy. By the end of this session, you will have a comprehensive understanding of the messaging problem space and will be better equipped to make informed decisions about whether and how to incorporate messaging into your distributed systems.

Комментарии • 3

  • @i.paradox
    @i.paradox 29 дней назад +9

    Laila's energy is on the next level even after lunch. 😅

  • @KibbleWhite
    @KibbleWhite 28 дней назад

    We're using the saga concept for data extractions from multiple micro services, which pulls data from each service and then stores it in a format ready for later export. Each extraction request has an expiry datetime.