Bit Syntax in Erlang
One of the often under-appreciated features of Erlang is its Bit Syntax for parsing and pattern matching binary data at a bit level. For instance, to pare TCP segments you can write something along the line of:
The same capability can be applied to anything binary protocols, such as video encoding, imaging, or UDP.
Imitating with F# Computation Expressions
Whilst this capability is not built into F#, or any other language that I know of for that matter, we do have a very powerful, and robust feature in F# in Computation Expressions.
With computation expressions, I was able to create a small library that allows you to write and read data to and from a stream at a bit level. With the bitWriter and bitReader workflows you will be able to write and parse TCP headers with code like the following:
The library is available via Nuget:
please give it a try, and let me know if you find any bugs here.
p.s. there is still much work to be done on the library. For instance, it’s allocating a new buffer array for each workflow rather than using a buffer pool. If you find this library useful and in need for greater performance, please feel free to contribute and help improve the performance of this library.
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 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. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, 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