We've implemented storing images to S3 from GAE for http://www.myclasses.org/ and pretty happy with results.
There is a 2 factors problem with serving images from GAE's blob-store: 1. Generation of get_serving_url takes a while. If you have many images to serve on a single page (*e.g. list if classes and their avatars in our case*) it can really slow your code and as result cost you money. So you don't want to do it on every page rendering. 2. We tried to cache the URL returned by get_serving_url() but it occurred it expires in a while (may be days or weeks) and there is no clear understanding when exactly and how to invalidate the URLs or HTML of pages we generate & cached in DB. With S3 we can have static & stable URL what is perfect for us. And in conjunction with CloudFrount it works really fast - we see noticeable improvements in client pages rendering by browsers. We used "boto" library to work with S3 that is not coupled with Django in any way (*as far as I know*) so you can try it as well. Good luck, Alex Founder & Lead Dev @ Petamatic.com On Tuesday, 4 December 2012 16:32:31 UTC-4, Emmanuel Mayssat wrote: > > They are several discussion about storing images in database (blob) versus > filesystem (s3). > Did anyone implement an app on GAE with an image interface on S3? > > I am not even sure where to start.... > > Django has a > http://django-storages.readthedocs.org/en/latest/index.html > but I use webapp2.... > > Thanks for any info, > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/GCtIWJ99pIcJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
