- a key-value stored modeled caching system that can run functions during set/get, have expiry, counters, counters that wait for N as a buffer before running transactions, and machine learning - all as primitives. the tail-recursive processes acting as mini-servers holding state and the best thing is that you have a mini-automatic scaling if you combine this well with expiring of processes. increase load when there's a need. they die when there's no more need/lesser traffic.<p>- a distributer crawler that works with python. from a typical rdbms approach that brought down creating inverted index's from more than an hour to few seconds. the euroka moment was when we stopped porting/writing for another language, sequentially, for-loop style approach to a more - processes and message passing. big 'why didnt i do this moment' a few years ago!<p>- a website , dashboard for the ad/content network using yaws on the LYME stack<p>- and btw - all that rumour about unicode is just bs. actually it was a blessing for us that content aka strings are just integers which when converted to binaries not only takes less space, pattern matches like a dream but all of a sudden your sytem can handle any language because to it - it's all just integers, english or swahili. that was a huge bonus even when getting investors, new untapped market opp's.<p>- an ad network, ( content network i guess without saying)<p>- a fire-and-froget thumbnail/screenshot system with queues & talking to imagemagick . i love writing and fire-and-forget tools, and with erlang, its so darn easy to write proceses's that have a life of their own. sure at some point you need to compromise on erlang's unique ability to handle RAM vs giving that up to research on how to handle large mnesia tables ( mnesia = inbuild db that has a limit on size of tables) . but it's worth the tradeoff.<p>case in point - our idea of scaling was...'reducing nodes' ie increasing efficiency<p>-2008 a million hovers in the year, 4 nodes<p>-2009 a million hovers every month, 3 nodes<p>-2010 a million hovers every week, 2 nodes
i could bring it down to 1 node for doing the tasks as well, on just one 1 8gb RAM node.<p>the idea of reducing your costs, means that much lesser to profitability. ( we're now profitable, pretty much on auto-pilot on the backend, the 3-4 member team concentrating on increasing toplines,sales now )<p>in addition...
- a wrapper to iui for nitrogen framework for building iphone webapps easily
- wrappers to tokyocabinet ive contributed to called medici
- remember writing wrappers to other things like rrd, aws utils, etc<p>all of the above have been used at hover.in, more at <a href="http://slideshare.net/bosky101" rel="nofollow">http://slideshare.net/bosky101</a><p>there's nothing i can think of that i wont/cant do in erlang anymore.<p>~B
@hoverin