We see your exact Dalvik problem on deepl.com as well. We get a constant flood of those requests, sometimes subsiding. They are globally distributed, preliminary in lower-income countries. We have tried lots of things, like letting them just time out, returning different errors, redirecting of many sorts including Android intents, no solution. They now made it to our permanent blocklist and we just deal with the useless additional traffic.
We are still hyper curious what on earth is loading us and for what reason though. AFAIK we couldn't see translation requests from them, just loading our website.
7$/user/month is pretty reasonable IMHO. Of course only for companies with 500 users. But even if you buy the 500 seat package for 100 users it's just 35$/user/month, compared to normal engineering salaries this is absolutely negligible.
As cool as this is, the "20x improved efficiency" is not what that paper says it seems:
> Over the course of the optimisation, CO2 fixation efficiency in the CETCH cycle improved by almost a factor of 20 until version 5.4 (Fig. 2).
> This is comparable to the few reported attempts to measure the CBB cycle in cell extracts (1 to 3 nmol min−1 mg−1 CBB cycle protein,
So what it actually says is: They improved CETCHs efficiency by 20x during the development, but it is not 20x more efficient than plants, but rather comparable (although it seems hard to measure what plant efficiency is)
I would suggest node.js - it makes it really easy to not shoot yourself in the foot. The async nature allows for concurrency, something you can't easily archieve with e.g. ruby and python. And while you are at it, try out hapi.js: http://hapijs.com/ - my favorite tool for writing request proxies (which i do for a living :D )