Solutions: Retlang

So far, I have listing the flaws of locks as an attempt to push you, my dear readers, out of this dead-end.

But so far, I have been avoiding the solution space, purposely. This post will end that!

I like immutability and message passing, therefore I suggest you look into retlang/jetlang (C#/java). Based on the actor model, it offers a nice API helping the implementation of scalable services. It has been around for a few years now, and it clearly provides value.

It turns out the framework I designed working here has similarities with it, but it uses a different approach, offering extra services without the obligation of the actor model.

I will share its design in future posts!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.