3 ms·
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
by vyrotek 16y ago
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).
Now thats cool. Each tenant basically gets their own set of data, cache and queues?
I can only hope that Windows Azure will step up and provide some similar functionality.
- detst 16y agoOne code base. You set a namespace and all datastore, memcache, and task queues operations are performed in that space. So: from google.appengine.api.namespace_manager import set_namespace set_namespace('user1') Now everything is done in the 'user1' namespace. EDIT: http://code.google.com/appengine/docs/python/multitenancy/multitenancy.html http://code.google.com/appengine/docs/python/multitenancy/mu... gives more details using a "namespace manager" but I think my example above answers your question so I'll leave it as-is.
- gmosx 16y agoMultitenancy is a killer feature, very useful for Google Apps Marketplace offerings. App Engine is slowly transforming to a true 'general-purpose' platform.
- checker659 16y agoYou're right. If this feature had been available when I was working for a client few months back, it would have saved me a lot of time.
- toddh 16y agoI didn't read if this is reflecting in billing, that is, can I have a particular customer pay for the resources they use?