Ray
@xbeco.bsky.social
Platform Engineer who take care of some Lambda on production
YAML should be dumped into trash bin.
900+ Lambda
100M ish invocation per day
YAML should be dumped into trash bin.
900+ Lambda
100M ish invocation per day
I think I can update my profile.
We committed to reduce this numbers, but it’s still going up slowly.
Still have a lot of things need to do .
We committed to reduce this numbers, but it’s still going up slowly.
Still have a lot of things need to do .
December 23, 2024 at 1:58 PM
I think I can update my profile.
We committed to reduce this numbers, but it’s still going up slowly.
Still have a lot of things need to do .
We committed to reduce this numbers, but it’s still going up slowly.
Still have a lot of things need to do .
DynamoDb can integrate with kinesis out of box. It’s a new feature in this year. IMHO, it’s better.The DynamoDb stream has a quota limitation. Per table only can have two steams.
Before it, we have to hook a lambda to publish it to a kinesis, so our data team and backend can consume it in both
Before it, we have to hook a lambda to publish it to a kinesis, so our data team and backend can consume it in both
DynamoDB + SQL? Learn how to stream DynamoDB data to S3 in real-time and query it with Athena SQL, combining NoSQL scalability with SQL flexibility. #AWS #ServerlessArchitecture #DataEngineering www.serverlesslife.com/Query_Dynamo... /cc @cdk.dev
Query DynamoDB with SQL using Athena - Leveraging EventBridge Pipes and Firehose (2/2)
With the help of EventBridge Pipes and Firehose, you can export DynamoDB data to S3 in near real-time, enabling you to query it using SQL via Athena.
www.serverlesslife.com
November 11, 2024 at 11:06 PM
DynamoDb can integrate with kinesis out of box. It’s a new feature in this year. IMHO, it’s better.The DynamoDb stream has a quota limitation. Per table only can have two steams.
Before it, we have to hook a lambda to publish it to a kinesis, so our data team and backend can consume it in both
Before it, we have to hook a lambda to publish it to a kinesis, so our data team and backend can consume it in both
For the light events, there is another pro is the schema compatibility. It’s kinda often the publisher will update the new event payload, adding new fields or add new enum items, etc. or remove fields. The light one have less fields and less chance to remove fields.
Ever questioned how much info you should pack in your events? Here are the pros & cons of each approach, and when to use which.
theburningmonk.com/2024/11/when...
theburningmonk.com/2024/11/when...
When to use Light Events vs. Rich Events in Event-Driven Architectures
Understand the differences between light events and rich events in Event-Driven Architecture. Learn when to use each approach.
theburningmonk.com
November 11, 2024 at 10:54 PM
For the light events, there is another pro is the schema compatibility. It’s kinda often the publisher will update the new event payload, adding new fields or add new enum items, etc. or remove fields. The light one have less fields and less chance to remove fields.
That’s nice
But when 🙂 they can support find the root cause within nested stack. Previously we have to scroll down many pages and jump to 5 depth nested stack to find the root cause.
Many developers gave us in the first page and throw the issue to infra or platform team to find it
Check this out! CloudFormation is getting a new Timeline View, showing exactly which parts of your deployments are taking up most time. It isn't showing up in my console yet but I'm sure it'll be there soon.
https://aws-news.com/article/01931d35-5421-db9a-fc76-530049444b3b
https://aws-news.com/article/01931d35-5421-db9a-fc76-530049444b3b
November 11, 2024 at 10:49 PM
That’s nice
But when 🙂 they can support find the root cause within nested stack. Previously we have to scroll down many pages and jump to 5 depth nested stack to find the root cause.
Many developers gave us in the first page and throw the issue to infra or platform team to find it
SAM application for lambda?
What a cave age. Why we are still using YAML? AWS have a better one, CDK! Why can we just support it CDK at the first place.
Configure a lambda to consume a SNS topic with FIFO SQS + a DLQ those standard pattern in CFN template is a huge pain!
What a cave age. Why we are still using YAML? AWS have a better one, CDK! Why can we just support it CDK at the first place.
Configure a lambda to consume a SNS topic with FIFO SQS + a DLQ those standard pattern in CFN template is a huge pain!
AWS Lambda developers, this one's for you! The enhanced local IDE experience now lets you test, debug, and build Lambda functions right from your IDE.
aws.amazon.com/blogs/comput...
#AWS #Serverless #DeveloperExperience
aws.amazon.com/blogs/comput...
#AWS #Serverless #DeveloperExperience
Introducing an enhanced local IDE experience for AWS Lambda developers | Amazon Web Services
AWS Lambda is introducing an enhanced local IDE experience to simplify Lambda-based application development. The new features help developers to author, build, debug, test, and deploy Lambda applicati...
aws.amazon.com
October 31, 2024 at 10:54 PM
SAM application for lambda?
What a cave age. Why we are still using YAML? AWS have a better one, CDK! Why can we just support it CDK at the first place.
Configure a lambda to consume a SNS topic with FIFO SQS + a DLQ those standard pattern in CFN template is a huge pain!
What a cave age. Why we are still using YAML? AWS have a better one, CDK! Why can we just support it CDK at the first place.
Configure a lambda to consume a SNS topic with FIFO SQS + a DLQ those standard pattern in CFN template is a huge pain!