Yan Cui
I help clients go faster for less using serverless technologies.
This article is brought to you by
Don’t reinvent the patterns. Catalyst gives you consistent APIs for messaging, data, and workflow with key microservice patterns like circuit-breakers and retries for free.
NOTE : read the rest of the series, or check out the source code.
If you enjoy reading these exercises then please buy Crista’s book to support her work.
Following on from the last post, we will look at the Declared Intentions style today.
Style 23 – Declared Intentions
Constraints
- Existence of a run-time typechecker.
- Procedures and functions declare what types of arguments they expect.
- If callers send arguments of types that aren’t expected, the procedures/functions are not executed.
The problem of type checking is a solved problem in statically typed languages, so by programming in F# there’s almost nothing we need to really do for this style.
Using the same solution from the Pipeline (aka functional) style, I have added a few explicit type declarations to better comply with the constraints.
You can find the source code for this exercise here.
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 for quickly levelling up your serverless skills.
- 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.
- Join my community on Discord, ask questions, and join the discussion on all things AWS and Serverless.
Pingback: F# Weekly #10, 2016 | Sergey Tihon's Blog