Hi, welcome to another weekly update.
Designing serverless applications with AWS Lambda
I’m running a live online training session with O’Reilly on April 15th and 16th. The session would provide some hands-on exercise for getting started with AWS Lambda and the Serverless framework, and provide you with the tools you need to design serverless applications with Lambda. This is an intermediate level session, and runs for a total of 6 hours over the two days. It is free for SafariBooksOnline subscribers, but you can also take advantage of the free trial and take this session as part of the free trial.
You can find out more about the session and register here.
DynamoDB TTL as an ad-hoc scheduling mechanism. I explored the idea of using DynamoDB TTL and DynamoDB Streams as a way to implement a scheduling service for ad-hoc tasks. I looked at how this system can be implemented, and how well it works in terms of scalability and precision. After running some experiments I found that, this solution is fairly imprecise. Tasks are executed an average of 10 minutes behind their scheduled time.
Understanding the scaling behaviour of DynamoDB OnDemand tables. I ran a number of experiments to see how DynamoDB manages the scaling of an OnDemand table. I was impressed with what I found – OnDemand tables can support up to 4000 ops/s out of the box. You will still get throttled when you exceed this initial limit. But OnDemand tables would also autoscale and adapt to your peak throughput, so that in the future you won’t experience throttling when you experience the same spike again. Overall, I feel confident about OnDemand tables and think they should be the default for anyone using DynamoDB.
Quite a busy couple of week coming up! If you see me at one of these events, please grab me and say hi :-D
28th March – I’ll be speaking about serverless and FinDev at CloudConf in Turin.
29th March – I’ll be speaking about serverless observability at ServerlessDays Amsterdam.
1st April – I’m joining a star-studded lineup of speakers on 1st April for OpenInfraDays in London. And I’m gonna be talking about serverless, and why it’s more FinDev than it’s DevOps.
2nd April – I’ll be taking a deep dive into how we built a social network on serverless at the AWS Community Summit in Manchester.
3rd April – I’ll be speaking about serverless observability at CodeMotion Amsterdam.
11th April – I’m honoured to be the opening keynote for the first ever ServerlessDays Zurich! I’ll discuss the journey to serverless, the co-evolution of development practices and where we are headed with serverless.
19th April – I’ll be talking about running serverless in production at DevExperience in Iasi. I will also run a one-day workshop after the main event as well.
Enjoy what you’re reading? Subscribe to my newsletter and get more content on AWS and serverless technologies delivered straight to your inbox.
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong