3 ms·
This was interesting because I've never seen Go used in production yet. However, the solution is not optimal for performance (as his benchmarking suggests is on
by danielrhodes 15y ago
This was interesting because I've never seen Go used in production yet. However, the solution is not optimal for performance (as his benchmarking suggests is one of the goals).
If there is a finite number of possible images and each image takes CPU time to generate, then why not lazy cache the images in a CDN after generating them once?
- cma 15y agoThe more complicated something is, the more chances for failure there are. Remember, this was only for compositing the image that would be shared to google plus -- the one in the browser is done client-side.
- enneff 15y agoThis works exactly as you describe - the app sets a cache header on the response and Google's geographically distributed front end servers will serve the cached response. You get all this for free by using App Engine.
- luriel 15y agoThere are quite a few people using Go in production already, see: http://go-lang.cat-v.org/organizations-using-go http://go-lang.cat-v.org/organizations-using-go