3 ms·
As a heavy user of AppEngine/Java in the early days, I don't think AppEngine/Java was every really viable. The long, long startup times were absolutely brutal f
by mmastrac 5y ago
As a heavy user of AppEngine/Java in the early days, I don't think AppEngine/Java was every really viable. The long, long startup times were absolutely brutal for scaling (30s-1min+, even w/ridic. work to optimize).
I stopped using it ~2014, but at that point it felt like it was going to go anywhere at all. The AppEngine environment just needed ways to pre-warm/pre-JIT (or even a snapshot function) to make this feasible on the underpowered instances that used to run it.
I also used a ton of AppEngine/Python (and still do on some of my personal single-serve sites - ie progscrape.com) and that was just so much better overall. Given the heavy use of caching, none of my AppEngine/Python sites ever incur a bill of >$0.10 per month.