Lambda

auto-create CloudWatch Alarms for APIs with Lambda

In a pre­vi­ous post we dis­cussed how to auto-sub­­scribe a Cloud­Watch Log Group to a Lamb­da func­tion using Cloud­Watch Events. So that we don’t need a man­u­al process to ensure all Lamb­da logs would go to our log aggre­ga­tion ser­vice. Whilst this is use­ful in its own right, it only scratch­es the sur­face of what …

auto-cre­ate Cloud­Watch Alarms for APIs with Lamb­daRead More »

AWS Lambda — monolithic functions won’t help you with cold starts

After my post on mono­lith­ic func­tions vs sin­­gle-pur­­posed func­tions, a few peo­ple asked me about the effect mono­lith­ic func­tions have on cold starts, so I thought I’d share my thoughts here. The ques­tion goes some­thing like this: Mono­lith­ic func­tions are invoked more fre­quent­ly so they are less like­ly to be in cold state, while sin­­gle-pur­­posed …

AWS Lamb­da — mono­lith­ic func­tions won’t help you with cold startsRead More »

Serverless observability brings new challenges to current practices

This is a the first in a mini series that accom­pa­nies my “the present and future of Server­less observ­abil­i­ty” talk at Server­less­Conf Paris and QCon Lon­don. part 1 : new chal­lenges to observ­abil­i­ty <- you’re here part 2 : first par­ty observ­abil­i­ty tools from AWS part 3 : 3rd par­ty observ­abil­i­ty tools part 4 : the future of Server­less observ­abil­i­ty 2017 …

Server­less observ­abil­i­ty brings new chal­lenges to cur­rent prac­ticesRead More »

AWS Lambda — how best to manage shared code and shared infrastructure

In the last post I dis­cussed the pros & cons of fol­low­ing the Sin­gle Respon­si­bil­i­ty Prin­ci­ple (SRP) when mov­ing to the server­less par­a­digm. One of the ques­tions that popped up on both Twit­ter and Medi­um is “how do you deal with shared code?”. It is a FAQ when­ev­er I speak at user groups or con­fer­ences about AWS Lamb­da, along­side “how do …

AWS Lamb­da — how best to man­age shared code and shared infra­struc­tureRead More »

AWS Lambda — should you have few monolithic functions or many single-purposed functions?

A fun­ny moment (at 38:50) hap­pened dur­ing Tim Bray’s ses­sion (SRV306) at re:invent 2017, when he asked the audi­ence if we should have many sim­ple, sin­­gle-pur­­posed func­tions, or few­er mono­lith­ic func­tions, and the room was pret­ty much split in half. Hav­ing been brought up on the SOLID prin­ci­ples, and espe­cial­ly the sin­gle respon­si­bil­i­ty prin­ci­ple (SRP), …

AWS Lamb­da — should you have few mono­lith­ic func­tions or many sin­gle-pur­posed func­tions?Read More »

You need to use structured logging with AWS Lambda

This is a les­son that I wished I learnt when I first start­ed using AWS Lamb­da in anger, it would have made my life sim­pler right from the start.  But, we did get there before long, and it allowed us to track and include cor­re­la­tion IDs in our log mes­sages (which are then pushed to an ELK stack)which would …

You need to use struc­tured log­ging with AWS Lamb­daRead More »

I’m afraid you’re thinking about AWS Lambda cold starts all wrong

When I dis­cuss AWS Lamb­da cold starts with folks in the con­text of API Gate­way, I often get respons­es along the line of: Meh, it’s only the first request right? So what if one request is slow, the next mil­lion requests would be fast. Unfor­tu­nate­ly that is an over­sim­pli­fi­ca­tion of what hap­pens. Cold start hap­pens once for …

I’m afraid you’re think­ing about AWS Lamb­da cold starts all wrongRead More »

AWS Lambda — use the invocation context to better handle slow HTTP responses

With API Gate­way and Lamb­da, you’re forced to use rel­a­tive­ly short time­outs on the serv­er-side: API Gate­way have a 30s max time­out on all inte­gra­tion points Server­less frame­work uses a default of 6s for AWS Lamb­da func­tions How­ev­er, as you have lim­it­ed influ­ence over a Lamb­da function’s cold start time and have no con­trol over the amount of …

AWS Lamb­da — use the invo­ca­tion con­text to bet­ter han­dle slow HTTP respons­esRead More »

Applying principles of chaos engineering to AWS Lambda with latency injection

This is part 2 of a mul­ti­part series that explores ideas on how we could apply the prin­ci­ples of chaos engi­neer­ing to server­less archi­tec­tures built around Lamb­da func­tions. part 1: how can we apply prin­ci­ples of chaos engi­neer­ing to Lamb­da? part 2: laten­cy injec­tion for APIs <- you’re here part 3: fault injec­tion for Lamb­da …

Apply­ing prin­ci­ples of chaos engi­neer­ing to AWS Lamb­da with laten­cy injec­tionRead More »

How can we apply the principles of chaos engineering to AWS Lambda?

This is the first of a mul­ti­part series that explores ideas on how we could apply the prin­ci­ples of chaos engi­neer­ing to server­less archi­tec­tures built around Lamb­da func­tions. part 1: how can we apply prin­ci­ples of chaos engi­neer­ing to Lamb­da? <- you’re here part 2: laten­cy injec­tion for APIs part 3: fault injec­tion for Lamb­da …

How can we apply the prin­ci­ples of chaos engi­neer­ing to AWS Lamb­da?Read More »

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