so, its been about 2 weeks, my fascination with erlang was as short lived as a teenage holiday romance.  the concurrent language which would probably topple all others if the overheads weren’t so much.  erlang has a huge learning curve, don’t think just cause you dabble in a bit of ruby you will pick up this language in one go

i’m sure it will take a few years of dedication to get the best of this beast.  as for the yaws server i couldn’t find much fault.  and according to tests this is a solid winner.  erlyweb was a bit of a hickup.  from version incompatibilities to the dreaded ‘//’ in the url (i think i might have gotten the sour deal of the experience).

so for now my quest to conquer erlang seem a bit like an empty dream, but my quest continues….with nitrogen…some day

a lot of focus on scalability and performance.  that being said – i’ve decided to be proactive and try out a stack i’m totally unfamiliar with, but apparently with great potential.

lyme – linux, yaws, mysql, erlang

linux - the tried and tested platform, open-source, and where all good things start.

yaws - yet another web server written in erlang, supposedly outperforms apache with throughput and parallel sessions.

mysql – i’m just a big fan, what can i say

erlang -  the language, created as a general purpose, concurrent language

so finally i got my lyme stack running on my machine – so now for the tedious process of evaluating it, and maybe do something like a simple user-to-user subscription service.  like the friends features of facebook

i’ll keep you informed with my findings, with a couple of code examples and a walkthrough of my experience.