-URL requests are matched with Erlang patterns (and possibly some regexes with Nginx)
-Python/ Erlang bridge done with internal REST Api
-most unstructured data stored in CouchDB
-requests end up in RabbitMQ message queue
-how message queue and rules engine (collection of state machines) match up buyers and sellers is not explained
-how transactions between buyers and sellers are stored by appending to long files is not explained
-how either these long files are spread out to many machines, or how CouchDB is spread out is not explained
Interesting talk, but except for the buzzwords they didn't reveal much of their internals.
I'm not trolling. Erlang is clearly ideal for this kind of thing. I wonder what kind of advantage it will give them?
-URL requests are matched with Erlang patterns (and possibly some regexes with Nginx)
-Python/ Erlang bridge done with internal REST Api
-most unstructured data stored in CouchDB
-requests end up in RabbitMQ message queue
-how message queue and rules engine (collection of state machines) match up buyers and sellers is not explained
-how transactions between buyers and sellers are stored by appending to long files is not explained
-how either these long files are spread out to many machines, or how CouchDB is spread out is not explained
Interesting talk, but except for the buzzwords they didn't reveal much of their internals.