The author couldn't be more right about picking an asynchronous driver. It makes me wonder how long it will take for the official MongoDB drivers to adopt this approach too. I've been using ReactiveMongo for Scala for the past two months and would recommend it without hesitation.
Asynchronous driver isn't always needed, but he was working with Tornado, an asynchronous framework. Using anything non asynchronous that has the possibility to block for any significant period of time (i.e. network call or database call) with tornado defeats the whole purpose. Hardly MongoDB's fault.
Comments
The author couldn't be more right about picking an asynchronous driver. It makes me wonder how long it will take for the official MongoDB drivers to adopt this approach too. I've been using ReactiveMongo for Scala for the past two months and would recommend it without hesitation.
Asynchronous driver isn't always needed, but he was working with Tornado, an asynchronous framework. Using anything non asynchronous that has the possibility to block for any significant period of time (i.e. network call or database call) with tornado defeats the whole purpose. Hardly MongoDB's fault.