3,403 karma · joined November 30, 2009
I'm setting up an Atlanta office and we're looking for our first development hire in the US. If you like mobile apps, wouldn't mind the idea of travel to Latin America (or North America if you're in Argentina), email me - chad@inaka.net.
I had the idea of bringing in say a few thousand USD/month (I have an office and a number of things like random office lunches, office rent, nespresso capsules, snacks, etc are for various reasons not payable via a check from a business account.) I could buy say $1500 USD in bitcoins but then I couldn't find people who are not miners to take the other side of the transaction that had enough bitcoins to buy $8000 to $12,000 ARS in one transaction.
WHY would that be useful? Well, if I have $1500 USD of bitcoins, I can get the "blue" rate of 8.05 * 1500 = $12,075 ARS. If I wire myself $1500 USD from outside Argentina, I'll get $8092 ARS. So, imagine I could use bitcoins to do the transaction. I'll get about 40% more money if someone properly values the bitcoin to the peso.
What we need is the coinbase of Argentina, but then being "legal" would kind of defeat the whole value of bitcoins in such a warped economy. Just check out http://dolarblue.net/ for the TWENTY different ways to convert ARS to USD/EUR, etc. Argentina is not a place you are going to setup a legal bitcoin exchange and have it last very long.
iex(1)> f = fn x -> x + 1 end
#Function<erl_eval.6.82930912>
iex(2)> f()
(UndefinedFunctionError) undefined function(stack trace trimmed...)
iex(2)> f.(1)
2
It's unclear whether the acquisition will be a success, but if it is a success the article's reasons will be irrelevant. If it isn't a success, those will not be the reasons why it failed.
There are whole companies who make elaborate servers that speak simple protocols. Membase is essentially a much more elaborate, multi-server replicated database that speaks the Memcache protocol.
We started edis as an experiment to teach some developers Erlang. We had a use case that was quite interesting at the time, so it was a great way to teach Erlang while working through some interesting database scenarios.
Imagine you have a bunch of users come into a site and they'll hit the server for an hour and then go away for at least a week, maybe more, like the demographics around a popular TV show. Imagine you need to handle a HUGE number of users for that hour, but after that hour, you have less than 1/10th of 1% of those users during the week. Also, imagine that you are pretty happy with Redis's speed, but that you've outgrown what you can comfortably handle on one server and so you are happy to tolerate less speed for more space.
This is a really nice use case for a disk-backed Redis server.
It's not the only option, of course, but we didn't need to store documents and we didn't need ACIDity.