App Engine: Multi-tenancy, High Performance Image Serving, Increased Quotas • Hacker News Board

Re: App Engine: Multi-tenancy, High Performance Image Serving, Increased Quotas

#21

Post by toddh » Wed, Aug 18, 2010, 3:21 PM UTC

c1sc0 wrote: post #15

rdzah wrote: post #4

I would love to have Appengine as an alternative to AWS, but what's a poor boy to do without his nodejs & cassandra?

I'd love to see how people are running map/reduce jobs on AppEngine.

There's a mapper API http://googleappengine.blogspot.com/2010/07/introducing-mapp.... It's a layer on top of task queues. No reduce yet.

Re: App Engine: Multi-tenancy, High Performance Image Serving, Increased Quotas

#22

Post by toddh » Wed, Aug 18, 2010, 3:23 PM UTC

gmosx wrote: post #11

vyrotek wrote: post #3

This allows you to easily serve the same app to multiple different customers, with each customer seeing their own unique copy of the app. I'm a bit confused by what this means exactly. Is it still 1 code base that you upload and manage or are you now just given the ability to upload different versions of code for each tenant? he API works will all of the relevant App Engine APIs (Datastore, Memcache, and Task Queues)…

Multitenancy is a killer feature, very useful for Google Apps Marketplace offerings. App Engine is slowly transforming to a true 'general-purpose' platform.

I didn't read if this is reflecting in billing, that is, can I have a particular customer pay for the resources they use?

Re: App Engine: Multi-tenancy, High Performance Image Serving, Increased Quotas

#23

Post by nir » Wed, Aug 18, 2010, 7:39 PM UTC

jasonkester wrote: post #16

kljensen wrote: post #2

Appengine keeps getting better and better.

Indeed. Unfortunately, it started off at "Terrible". I think it's finally moved past "Embarrassing", but it's still a long way from "Ready to use." Give them another couple years, and maybe they'll make it all the way to "Good". Unfortunately, lots of us got burned by it in the early days and we probably won't be coming back.

It depends what you use it for. For relatively small apps that don't need much system level tuning I find it pretty awesome. Scaling wise it's fantastic - I have an app serving >100k hits/day (admittedly doing very little for each hit) with no problem.