You can become a serverless blackbelt. Enrol to my 4-week online workshop Production-Ready Serverless and let me take you through building a production-ready serverless application from testing, deployment, security right through to observability. This workshop gives you hands-on experience building something with serverless technologies while giving you a broader view of the challenges you will face as the architecture matures and expands. By the end of the workshop, you should have a clear idea when serverless is a good fit for your system as well as common pitfalls you need to avoid.
Pattern matching is everywhere in F#, you can use it in let bindings, in function parameters, in for loops, everywhere, and it is totally amazing. It is in my opinion one of the best features of F#, and in functional languages in general, heck, Erlang goes as far as not having an assignment operator and everything is pattern matched instead (yup, that’s right, ‘=’ is the pattern match operator in Erlang, not assignment!). Once you’ve had a chance to work with it you’ll understand why those functional folks love it so much!
In terms of exception handling, consider this piece of code in C#:
Notice that the switch statement allows you to apply the same handler to multiple cases but not the catch statements, which leads to duplicated exception handling code. Wouldn’t it be nice if you don’t have to keep repeating yourself?
Now, let’s see how pattern matching in F# lets us do just that:
Pretty neat, right? Not only are you able to group handling code for different exceptions, you can also use wild card ( _ ) and when guards (e.g. | _ as ex when ex.Message.Contains(“Oops”) to match any exception whose message contains the term ‘Oops’) too, which give you a very fine control over which handler is used for what exceptions.
As the patterns are matched from top to bottom, if you move the wildcard pattern to the top you’ll receive a set of gentle warnings from the compiler letting you know that doing so will mean that each of the subsequent patterns will never be matched.
It’s also worth noting that whilst F# has try-catch and try-finally expressions, there is no try-catch-finally expression.
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new podcast Real-World Serverless where I talk with engineers who are building amazing things with serverless technologies and discuss the real-world use cases and challenges they face. If you’re interested in what people are actually doing with serverless and what it’s really like to be working with serverless day-to-day, then this is the podcast for you.
Check out my new course, Learn you some Lambda best practice for great good! In this course, you will learn best practices for working with AWS Lambda in terms of performance, cost, security, scalability, resilience and observability. We will also cover latest features from re:Invent 2019 such as Provisioned Concurrency and Lambda Destinations. Enrol now and start learning!
Check out my video course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. There is something for everyone from beginners to more advanced users looking for design patterns and best practices. Enrol now and start learning!
Are you working with Serverless and looking for expert training to level-up your skills? Or are you looking for a solid foundation to start from? Look no further, register for my Production-Ready Serverless workshop to learn how to build production-grade Serverless applications!
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 wrong about serverless and vendor lock-in
- You are thinking about serverless costs all wrong
- Just how expensive is the full AWS SDK?
- Many faced threats to Serverless security
- We can do better than percentile latencies
- 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
- Top 10 Serverless framework best practices