How to connect SNS to Kinesis for cross-account delivery via API Gateway

Leave a Comment / API Gateway, AWS, Kinesis, Lambda, Programming, Serverless, SNS / July 21, 2019

At DAZN (where I no longer work), the teams work with a number of third-party providers. They often have to synchronize data between different AWS accounts. SNS to SQS is the primary mechanism for these cross-account deliveries because: it was an established pattern within the organization DAZN engineers and third-party engineers are both familiar with …

How to connect SNS to Kinesis for cross-account delivery via API Gateway Read More »

Tweet
Share
+1
Share

Weekly update 29

Leave a Comment / Me, Weekly Update / July 7, 2019

Hi, welcome to another weekly update. This is my first update since moving to Amsterdam, and I have perhaps been indulging myself on Stroopwafel a little too much! Seriously, they’re so good, and available everywhere! Anyhow.. on with the update ;-) New posts Meet the family, the “other” AWS serverless services. In this post, I …

Weekly update 29 Read More »

Tweet
Share
+1
Share

AWS Lambda: how to share code between functions in a monorepo

Leave a Comment / AWS, Lambda, Programming, Serverless / June 30, 2019

A while back, a client asked me “how can I share business logic between services in a Node.js monorepo?”. The TL;DR of it is: Encapsulate the shared business logic into modules, and put them in a separate folder. In the Lambda handler functions, reference the shared modules using relative paths. Use webpack to resolve and …

AWS Lambda: how to share code between functions in a monorepo Read More »

Tweet
Share
+1
Share

Step Functions as an ad-hoc scheduling mechanism

Leave a Comment / AWS, Design Patterns, Lambda, Programming, Serverless, Step Functions / June 28, 2019

We previously discussed how you can implement an ad-hoc scheduling system using DynamoDB TTL as well as CloudWatch Events. And now, let’s see how you can implement the same system using AWS Step Functions and the pros and cons of this approach. As before, we will assess this approach using the following criteria: Precision: how …

Step Functions as an ad-hoc scheduling mechanism Read More »

Tweet
Share
+1
Share

AWS Lambda: how to detect and stop accidental infinite recursions

Leave a Comment / AWS, Lambda, Programming, Serverless / June 15, 2019

Lambda makes it easy to build event-driven architectures. Each function only needs to look after its own responsibilities. We chain them together through APIs, queues, streams, and other event sources. It’s a good way to build complex systems out of simple components. We need only managed services, and we only pay for them when we …

AWS Lambda: how to detect and stop accidental infinite recursions Read More »

Tweet
Share
+1
Share

How to log timed out Lambda invocations

Leave a Comment / AWS, Lambda, Programming, Serverless / June 14, 2019

Imagine the situation. It’s 3 AM, and PagerDuty alerts you that the number of 5XX errors has spiked. Something’s wrong. Strange, there are no error logs… Fortunately, we have enabled X-Ray tracing and I’m able to quickly find one of the traces for these 5XX errors. Sadly, the traces don’t offer any explanation for the …

How to log timed out Lambda invocations Read More »

Tweet
Share
+1
Share

ICYMI: five updates you’ve missed about Serverless Step Functions

Leave a Comment / AWS, Lambda, Programming, Serverless, Step Functions / May 23, 2019

Over the last 6 months, we have made the Serverless Step Functions plugin better and more useful. Here are the most impactful changes, in case you missed it! Support for intrinsic function One of the main pain points of using the plugin has long been that you needed to use fully-formed ARNs. As of v1.18.0 …

ICYMI: five updates you’ve missed about Serverless Step Functions Read More »

Tweet
Share
+1
Share

A self-healing Kinesis function that adapts its throughput based on performance

Leave a Comment / AWS, Design Patterns, Kinesis, Lambda, Programming, Serverless / May 20, 2019

I spent time with a client this week to solve an interesting problem – to adjust the number of concurrent requests to a downstream service dynamically based on response time and error rate. This is a common challenge when integrating with third parties, so we decided to share our approach so others might benefit from …

A self-healing Kinesis function that adapts its throughput based on performance Read More »

Tweet
Share
+1
Share

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close