deploying applicaiton to multiple customers

3 views
Skip to first unread message

gops

unread,
Nov 23, 2008, 5:00:47 AM11/23/08
to Google App Engine
Hi ,

I want to create an enterprise grade to do list -- and sell it to some
customer.

Is it possible , to deploy an application on different domain -- the
deployed application will use different database for each domain.

and manage it through single dashboard ?

If not possible right now , will it be in near future , say march ?

Roberto Saccon

unread,
Nov 23, 2008, 7:58:39 AM11/23/08
to Google App Engine
My understanding of the current situation is as follows:

- You either deploy one app for all domains (then you need to
implement the billing and quota stuff per domain on your own, that of
course doesn't make sense now with the preview quota limitations)

or

- You deploy for each customer you app with a different app-id (that
will be a maintenance nightmare if you have many customers)

regards
Roberto

hawkett

unread,
Nov 24, 2008, 7:52:42 AM11/24/08
to Google App Engine
It would be good to be able to support multiple app instances in a way
that provides an easy upgrade path - e.g. allow multiple app-id's in
app.yaml? Maybe thats got other problems associated with it, but it
is a common scenario when delivering SaaS that customers expect their
data to be partitioned away from other customers, and while in some
scenarios it might be god to be able to have each customer on a
different version of the application, it is more likely that we
upgrade all customers at once, and this is transparent to them - i.e.
one of the benefits of SaaS is you are always on the latest version of
the software. It would be possible t write an external script that
managed this deployment, but it would be good if GAE understood that
this was a common requirement and supported it. This issue

http://code.google.com/p/googleappengine/issues/detail?id=733

also highlights that we need a little more flexibility when deploying
customer apps - making the app-id unique obviously necessary - but
that shouldn't need to be exposed in the URL on custom domains.
Reply all
Reply to author
Forward
0 new messages