Okay, fine, I'll jump on the AI bandwagon.

This series on guitar set up by Gibson is pure gold. youtube.com/playlist?list=PL…

The DynamoDB Book Black Friday sale is live 🎉 Use the code 'DYNAMO2023' to get: - $20 off Basic - $40 off Plus - $80 off Premium - 35% off Team Licenses If you've been on the fence, this is a great time to pick it up learn DynamoDB 🙂

📣 Powertools for AWS Lambda (Python) 2.28 is out! 🔥 Request/Response data validation via types 🔥 OpenAPI & SwaggerUI for API Gateway REST/HTTP, ALB, Lambda Function URL, VPC Lattice 🫶 Inspired by FastAPI to ease migrations and more! github.com/aws-powertools/po… #aws #serverless

Hey! We launched a small but mighty library called AWS Integrated Application Test Kit to make integration testing easier for event-driven apps. It's in preview, and we would love your feedback on this! aws.amazon.com/blogs/compute… blogpost - aws.amazon.com/blogs/compute… #eventbridge

🚀Amazon EventBridge launch announcement 🚀 We've rolled out an additional 22 new CloudWatch Metrics for Event Bus. Metrics include API latency, event payload size, as well as number of successful, failed, and throttled events. aws.amazon.com/about-aws/wha…

The first post in the Serverless OpenTelemetry at scale series is out! In this installment we explore PostNL, the central event broker, the need for observability and the choice for OpenTelemetry. lucvandonkersgoed.com/2023/1…

I will be delivering two sessions at re:Invent 2023. BOA311 - Unlocking serverless web applications with AWS Lambda Web Adapter bit.ly/401tUYj SVS312 - Building serverless applications with Terraform bit.ly/48QsoMy Looking forward to seeing you in Las Vegas!

I took some time to organize my thoughts on Serverless, and wrote an article. This is the first time I've been able to fully express why I think Serverless is the future. When the shoulders of giants are offered, you'd do well to stand on them. lucvandonkersgoed.com/2023/1…

Recognition is like a dog’s own tail. It can get dizzy chasing and is not sustainable. Go on about learning, applying, and genuinely helping others, and many things including recognition, slowly but surely, will quietly follow.

“AWS Lambda based Serverless Observability using OpenTelemetry” is now live.... The guide covers observability best practices for Lambda based serverless #AWS #AmazonWebServices #AWSBlogs #Cloud #CloudComputing #Serverless #Lambda #OpenTelemetry bit.ly/3FaORqi

I've used this pattern before without knowing it has a name, now I know! It also reminds me of the "roll-up events" that @sheenbrisals talked about, which is the reverse of this - a summary event that comes after the individual events. serverlessland.com/event-dri…

I'm sad to report that the PostNL Event Broker project I'm responsible for has broken its two-year streak of no production incidents. In fact we failed to deliver about 40k events, and *did not even notice* until a customer told us 3 days later. So let's learn from it.

Haven’t found a leader or role model you longed yet? Consider becoming that person and be there for others.

what goes dev, must come ops

Software design is preparation for change.

At last, I can break out the news that... Powertools for AWS Lambda is now an official AWS team!!!!!!! This secures: 🤩 Long-term project sustainability 🤩 Feature parity across languages 🔥 New home docs.powertools.aws.dev 🚀 Plan beyond Lambda 1/ #aws #serverless

New Post! AWS Lambda can pre-warm your functions to reduce the number of cold starts, even when used on-demand! This post defines Proactive Initialization, compares benchmarks from multiple runtimes/workloads, and shows you how to measure this in your own functions! Link 👇

Exciting news! AWS Step Functions just got better with two major console enhancements! You can now view Lambda’s CloudWatch logs directly in our operator experience, making troubleshooting a breeze. Plus, we’ve got you covered with seamless support all Lambda integration methods.

I keep seeing people get confused on DynamoDB having 10GB partitions and thinking they need to design around it. This happened twice in the last week! Writing a long tweet to clarify. Two main takeaways: 1. The '10GB partition size' is rarely visible to you as a user. 2. You are not limited to 10GB of data for a given partition key (**if you don't have an LSI on your table**). Explanation: First, some vocab: The term 'partition' refers to a co-located subset of your data within a DynamoDB table. Partitions are ~10GB in size but can be larger or smaller. DynamoDB is a multi-tenant system with a huge fleet of storage nodes, and each storage node contains many partitions from many different tables. The term 'item collection' is used to refer to the set of records that share the same partition key in your table. Within the item collection, items are sorted according to the sort key. ----- DynamoDB assigns an item to a partition using the partition key (and, occasionally, the sort key). In most cases, a single partition will contain multiple item collections. Also, a single item collection will often be contained on the same partition. But this is not always the case! If your item collection exceeds 10GB, DynamoDB will split it across multiple partitions. If you are driving heavy traffic to your item collection and DynamoDB thinks it could serve it better across multiple partitions, it might split it across multiple partitions. But there's not necessarily a 1:1 mapping from partitions to item collections nor from item collections to partitions. However, if your table has a local secondary index (LSI), the rules change. Now, your item collection *must* fit within a single partition. This means the item collection any LSI replicas of it must be under 10GB. This is the only time the 10GB limit applies. This is pretty rare -- I recommend against LSIs in almost all scenarios, partly because of this limitation. But if you don't have an LSI, you don't need to worry about keeping your item collections under 10GB (for capacity reasons -- there may be query-based reasons to keep it smaller)! ✨ The more you know