Yan Cui
I help clients go faster for less using serverless technologies.
After reading this old post by Don Syme, I really liked the idea of wrapping the result of any computation into an option type to signify success and failure cases and stop subsequent computations on the first failure. It’s neat but I wanted to tweak a couple of things to make it more useful:
- exceptional cases are not handled right now
- being able to retry on exceptions will be very useful
- being able to dictate how many retries are made will be useful too
with those three points in mind, here’s the code I ended up with:
And some quick tests:
Let me know what you think and if there’s anything else I can tweak to make this more useful!
Whenever you’re ready, here are 3 ways I can help you:
- Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game. This is your one-stop shop to level up your serverless skills quickly.
- Do you want to know how to test serverless architectures with a fast dev & test loop? Check out my latest course, Testing Serverless Architectures and learn the smart way to test serverless.
- I help clients launch product ideas, improve their development processes and upskill their teams. If you’d like to work together, then let’s get in touch.
It’s really useful! Just hard to copy…nevermind
I made a gist of this https://gist.github.com/ImaginaryDevelopment/244f4c963cf3f9e5880dc25346933069
about to make what I consider to be some improvements, but I wanted to get the raw essence of your work running before moving forward. I’m not familiar with computation expressions, but what you’ve done here looks remarkably easy to follow compared to the other attempts I’ve seen at a concrete example.
Thanks