DynamoDB STREAMS & Lambda Triggers | .NET ON AWS | AWS Serverless | Amazon

Поделиться
HTML-код
  • Опубликовано: 5 авг 2024
  • DynamoDB Streams capture a time-ordered sequence of events in any DynamoDB table. It is also referred to as Change Data Capture. Whenever an application creates, updates, or deletes items in the table, DynamoDB Streams writes a stream record with the primary key attributes of the items that were modified. A stream record contains information about a data modification to a single item in a DynamoDB table.
    DynamoDB streams help decouple core application logic from the effects that happen afterward. It helps with scenarios where you want to replicate data, generate read models of your data, etc. It can also be used as an alternative for Transactions when you need to update across multiple sources.
    In this video, we will learn how to get started with DynamoDB streams and use Lambda functions using .NET to handle stream events. We will also look at the different configurations associated with the Lambda Triggers, handle exceptions, and different patterns of integrating with DynamoDB stream events.
    This video is sponsored by AWS and is part of the .NET on AWS Series.
    00:00 Introduction
    02:15 Enable DynamoDB Stream
    04:21 Create Lambda Function
    09:51 Lambda Trigger
    15:57 Test Lambda Dev env
    16:32 Extract Data from events
    23:36 Lambda Trigger Configuration
    26:30 Filtering Events
    27:33 Exception Handling
    31:46 SQS Dead Letter Queue
    36:53 - Integration Patterns
    38:30 Conclusion
    🔗 Getting Started with DynamoDB - www.rahulpnath.com/blog/aws-d...
    🔗DynamoDb Streams Integration Patterns - aws.amazon.com/blogs/database...
    🔗 Postman - www.postman.com/
    🔗JSON Web Token Builder - jwtbuilder.jamiekurtz.com/
    Additional Watching
    📹 Amazon DynamoDB - • AWS DynamoDB For The ....
    📹API Gateway REST API - Lambda Integration • AWS LAMBDA Proxy Integ...
    📹Amazon API GATEWAY - Introduction To REST APIs - • Amazon API GATEWAY - I...
    📹AWS API Gateway - HTTP API - • Amazon API GATEWAY - H...
    📹AWS Lambda - • AWS LAMBDA For The .NE...
    📹AWS Series - • .NET on AWS
    Come say hi! ✋
    🌍 Blog - rahulpnath.com/
    ✉ Subscribe to my Newsletter - www.rahulpnath.com/subscribe
    🐦Twitter - / rahulpnath
    📸Instagram - / rahulpnath
    🛠️ Uses rahulpnath.com/uses
    🎥 Recording Setup and Workflow - www.rahulpnath.com/blog/youtu...
  • ХоббиХобби

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

  • @parmarjitesh1979
    @parmarjitesh1979 2 года назад

    Rahul sir extremely great as always.
    I wish to be knowledgeable as you

    • @RahulNath
      @RahulNath  2 года назад +1

      So nice of you Jitesh! Happy to help you along. Feel free to reach out to me if you need help of any guidance. bio.link/rahulpnath

  • @ajaysonar662
    @ajaysonar662 Год назад

    This is great content Rahul ! I had to delete my lambda as I panicked after seeing it being triggered too many times after exception. This clears all my doubts. A question though, Can TTL on dynamo trigger a stream event? Thanks a ton.

  • @stadothesagsphinx21
    @stadothesagsphinx21 Год назад

    Hi Rahul, Thank you that was really informational. I am working on similar use case where the DynamoDB records are getting by Lambda and the records are sent to Firehose in another acount. My question is, If I set failed records to send to SQS queue. How would do I reprocess those failed records from SQS queue? Do I have to attach SQS as trigger to lambda ? If the trigger is not attached then how do i process these records manually so that I can make sure that the failed records are being sent to firehose ?

    • @RahulNath
      @RahulNath  Год назад

      yes Shyam you will have to process this with a trigger or manually triggered code to read from the queue. Hope you resolved the problem.