erlang: All content tagged as erlang in NoSQL databases and polyglot persistence
If you are asked to compare (or you just wonder about) the performance of link walking and map-reduce in Riak keep in mind the following details of how the two mechanism are implemented:
My emphasis on Bryan Fink’s email from Riak’s mailing list.
Original title and link: Riak Performance of Link Walking vs MapReduce ( ©myNoSQL)
There’s a bit of CouchDB in the project:
We’ve built an open-source product that automatically deploys, scales and distributes VoIP calls across the Internet on commodity or virtualized servers. It fully utilizes Erlang for VoIP logic as well as relies on other Erlang products like CouchDB and RabbitMQ. It’s got an awesome set of APIs and some other nifty features.
 talking about Membase and Erlang (what worked and what didn’t) at Erlang Factory Lite LA:
I haven’t got to learn Erlang yet, so I’m mostly bookmarking OJ’s 3 part tutorial for future read:
- ☞ Part 1
In Part 1 of the series we covered the basics of getting the development environment up and running. We also looked at how to get a really simple ErlyDTL template rendering
- ☞ Part 2
There are a few reasons this series is targeting this technology stack. One of them is uptime. We’re aiming to build a site that stays up as much as possible. Given that, one of the things that I missed in the previous post was setting up a load balancer. Hence this post will attempt to fill that gap.
- ☞ Part 3
In this post we’re going to cover:
- A slight refactor of code structure to support the “standard” approach to building applications in Erlang using OTP.
- Building a small set of modules to talk to Riak.
- Creation of some JSON helper functions for reading and writing data.
- Calling all the way from the Webmachine front-end to Riak to extract data and display it in a browser using ErlyDTL templates.
Original title and link: Tutorial: Developing in Erlang with Webmachine, ErlyDTL, and Riak (NoSQL databases © myNoSQL)