3 ms·
Yes, if the traffic of your web app is large and need tons of GAE instances, then the memory and warm-up problems will become much less severe. But if the traff
by tapirl 9y ago
Yes, if the traffic of your web app is large and need tons of GAE instances, then the memory and warm-up problems will become much less severe. But if the traffic is not large, then the two problems are the big obstacles to save spending and happy roll deployments.
One the other hand, Go is good for both low traffic and high traffic websites.
I disagree on "Go is a poor language for general business processing". The current Go runtime on GAE is very mature to build all kinds of websites.
- cube2222 9y agoI love Go and use it daily, but it really is inferior to other languages for general business processing. The lack of generics, and a nice map, filter, reduce, flatten workflow cause this for me. Sometimes I'll just use goderive then, but it still looks clunky. (No pipe or fluent API)