Serverless

You are thinking about serverless costs all wrong

The Register published an article right before Christmas 2018. It had a somewhat provocative title, and somehow it ended up in my inbox from a few different sources. I felt the whitepaper the article refers to provided some interesting analysis. But the case studies it used to make its point are not representative of what …

You are thinking about serverless costs all wrong Read More »

Production-Ready Serverless is coming to a workshop near you!

As we approach the completion of my video course Production-Ready Serverless, I have also delivered the course in a classroom setting with both SimplyBusiness and the DVLA in the UK. In the coming months, I will also be running public workshops at various conferences and user groups: AWS User Group 17th Oct @ The Telegraph, London (sold …

Production-Ready Serverless is coming to a workshop near you! Read More »

Step Functions : apply try-catch to a block of states

In my last post we talked about how we can implement semaphores with Step Functions. Another common scenario that many people have is to handle errors from a block of states like we’re used to with a try-catch block. try { step1() step2() step3() } catch (States.Timeout) { … } catch (States.ALL) { … } …

Step Functions : apply try-catch to a block of states Read More »

How to create IP-protected endpoints with API Gateway and Lambda

If you haven’t been paying close attention you might have missed the API Gateway announcement for resource policies. It later played a key role in supporting API Gateway private endpoints – a way to put your API inside a private VPC. To configure resource policies with the Serverless framework, you need to upgrade to v1.28.0 or …

How to create IP-protected endpoints with API Gateway and Lambda Read More »

Centralised logging for AWS Lambda, REVISED (2018)

First of all, I would like to thank all of you for following and reading my content. My post on centralised logging for AWS Lambda has been viewed more than 20K times by now, so it is clearly a challenge that many of you have run into. In the post, I outlined an approach of …

Centralised logging for AWS Lambda, REVISED (2018) Read More »

Step Functions: how to implement semaphores for state machines

Here at DAZN, we are migrating from our legacy platform into a brave new world of microfrontends and microservices. Along the way, we also discovered the delights that AWS Step Function has to offer, for example… flexible error handling and retry the understated ability to wait between tasks the ability to mix automated steps with …

Step Functions: how to implement semaphores for state machines Read More »

Video and slides for my talk “applying principles of chaos engineering to Serverless”

Hello, just a quick note to tell you that recording of my talk at the recent AWS User Group meetup is now live! In this talk, I introduced the core concepts of chaos engineering, and the challenges that the Serverless paradigm brings to the existing tools and practices we use. I then looked at techniques …

Video and slides for my talk “applying principles of chaos engineering to Serverless” Read More »

Video and slides for my talk “applying best parts of Microservices to Serverless”

Hello, just a quick note to tell you that recording of my keynote at ServerlessDays TLV is now live! In this talk, I looked at a number of important lessons we learnt from the Microservices world and how they are still relevant to us as move to Serverless, and we can apply past learnings and …

Video and slides for my talk “applying best parts of Microservices to Serverless” Read More »

auto-create CloudWatch Alarms for APIs with Lambda

In a previous post we discussed how to auto-subscribe a CloudWatch Log Group to a Lambda function using CloudWatch Events. So that we don’t need a manual process to ensure all Lambda logs would go to our log aggregation service. Whilst this is useful in its own right, it only scratches the surface of what …

auto-create CloudWatch Alarms for APIs with Lambda Read More »

You need to sample debug logs in production

It’s common practice to set log level to WARNING for production due to traffic volume. This is because we have to consider various cost factors: cost of logging : CloudWatch Logs charges $0.50 per GB ingested. In my experience, this is often much higher than the Lambda invocation costs cost of storage : CloudWatch Logs charges $0.03 …

You need to sample debug logs in production 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