This is encouraging! I wish there was more information about how this pattern evolved.
The destined lambda pattern capabilities are explained well, addressing reliability and beautifully separating code into smaller lambda functions. IMHO, that's why the pattern is interesting to discuss. The asynchronous lambda is really different. The payload limits are different too.
Software Architect working on enabling engineers to rapidly deliver serverless-first solutions in a Fortune 100 organisation - passionate about Serverless, AWS, dev.to/cdkpatterns, TCO, and CI/CD
Usually when I add a pattern I have loads of proven source material from AWS Heroes. On this one, I just made the connection myself so you’re right to do it justice it probably needs a detailed blog post on the theory behind it, the advantages, the disadvantages etc
Stupendous! The details just may help me understand where the pattern belongs. The pattern probably evolved, how did the lamdba destined pattern exactly evolve from the aforementioned stuff? I still wonder.
Software Architect working on enabling engineers to rapidly deliver serverless-first solutions in a Fortune 100 organisation - passionate about Serverless, AWS, dev.to/cdkpatterns, TCO, and CI/CD
To give a quick answer on where it evolved. I created the EventBridge ETL pattern (github.com/cdk-patterns/serverless...) which uses EventBridge and Lambdas for extracting, transforming and loading data from s3 to DynamoDB. The vast majority of the logic in the Lambda functions is for processing events from and sending events to EventBridge so the ability to reduce that code was what I went looking for. Lambda Destinations is an answer to that.
It's nice code. Looks like it will launch a stack instantly. Interesting roots, etl. I'm fiddling with different patterns to replicate one set of DynamoDB tables to another set and most etl patterns use S3 for millions of bytes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is encouraging! I wish there was more information about how this pattern evolved.
The destined lambda pattern capabilities are explained well, addressing reliability and beautifully separating code into smaller lambda functions. IMHO, that's why the pattern is interesting to discuss. The asynchronous lambda is really different. The payload limits are different too.
Usually when I add a pattern I have loads of proven source material from AWS Heroes. On this one, I just made the connection myself so you’re right to do it justice it probably needs a detailed blog post on the theory behind it, the advantages, the disadvantages etc
Stupendous! The details just may help me understand where the pattern belongs. The pattern probably evolved, how did the lamdba destined pattern exactly evolve from the aforementioned stuff? I still wonder.
To give a quick answer on where it evolved. I created the EventBridge ETL pattern (github.com/cdk-patterns/serverless...) which uses EventBridge and Lambdas for extracting, transforming and loading data from s3 to DynamoDB. The vast majority of the logic in the Lambda functions is for processing events from and sending events to EventBridge so the ability to reduce that code was what I went looking for. Lambda Destinations is an answer to that.
It's nice code. Looks like it will launch a stack instantly. Interesting roots, etl. I'm fiddling with different patterns to replicate one set of DynamoDB tables to another set and most etl patterns use S3 for millions of bytes.