[2022 AWS re:Invent] Building next-gen applications with event-driven architectures

by
세션 유형

Break out

세션명

Building next-gen applications with event-driven architectures

강연자
  • Eric Johnson, Principal Developer Advocate, AWS
세션요약자

김민철(Minchul Kim)

핵심내용 요약
  • Enterprise Integration Patterns
  • Synchronous request-response model
  • Asynchronous point-to-point model
  • Handling event duplication using idempotency
키워드
  1. Enterprise integration patterns
  2. Synchronous request-response model & Asynchronous point-to-point model
  3. Optimized integration & AWS SDK integrations
상세내용

Use Case:

  • Enterprise Integration Patterns
    • The appropriate level of coupling depends on the level of control you have over the endpoints
  • Synchronous request-response model

Asynchronous point-to-point model (queue)

  • 장점
    • 시간적 결합을 줄임
    • 리시버 실패에 강함
    • 리시버가 소모되는속도를 컨트롤
    • Dead-letter queue (DLQ) for errors
    • 단 한명의 리시버만이 메세지를 사용
  • 단점
    • 상관분석
    • 백로그 복구 시간
    • 멀티테넌시 시스템 공평성
  • Amazon Simple Queue Service (Amazon SQS)

Asynchronous point-to-point model (router)

  • 단점
    • 위치 결합 증가
    • 발신자 routing logic 유지
    • Sender complexity 증가 

Asynchronous point-to-point model (bus)

  • 장점
    • 위치 결합 감소
    • 발신자와 수신자에게 효율적
  • EventBridge
    • Pay-as-you-go event bus service

Step functions integration types

  • Optimized integration
  • AWS SDK integrations

Handling event duplication using idempotency

Idempotency tokens

  • Idempotency tokens은 메세지를 확인하여 받는자가 중복되지않는것을 방지
    • 클라이언트로 생성됨
    • 메시지 별로 유일함
    • 정해진 필드사용

Retried idempotent request sequence

Leave a Comment