KCWilson - by my reading it's people accessing apps deployed on appengine. The expectation is these will be users on your intranet. For public apps - websites etc. - there'll be a different billing model which I imagine will be the same as the current AppEngine system, but pricier.
Looks very interesting but are you guys going to sort out the full text search story at least for this "for business" version? That is the biggest show stopper for me and my company right now and I do not think we are the only ones struggling with this.
AdSense - which is responsible for more than 90% of Google's revenue - does not even have a phone number! Nor an email address (it auto-rejects you to go to the forums)! And the forums aren't even monitored by a Google employee!
The Nexus One was released without ANY support whatsoever!
I don't think the old Goog has enough experience with support, or respect for it - especially enterprise class support - to take this to serious heights.
Only time will tell. But after trying for seven months to solve a simple AdSense problem that would have taken 2 mins over the phone - I certainly won't be the first guinea pig.
+1 on Manjoor's comment. These two constraints are my biggest source of headaches with GAE. The 30 second limit, coupled with the horrible performance of JDO, forced me to rewrite a good chunk of my app using the native API. The lack of SQL forced me to sync to an external MySQL database for reporting capabilities. Not having to do both would have cut at least 20% of the sum development time.
Could you share a bit more detail about the "dedicated full-featured SQL servers" coming in Q3? Is it going to be an existing (OS?) database engine, something home-grown, or ...?
Ummm...so does this mean things like SSL on custom domains, or SLAs won't come to standard App Engine? This would suck. Hugely.
ReplyDeleteSounds promising. Is that a maximum of $1000 per month per application or across all applications?
ReplyDelete"Each application costs just $8 per user, per month up to a maximum of $1000 a month. Pay only for what you use."
ReplyDeleteIs this developers accessing the app engine for business app or people access apps deployed running on app engine?
KCWilson - by my reading it's people accessing apps deployed on appengine. The expectation is these will be users on your intranet. For public apps - websites etc. - there'll be a different billing model which I imagine will be the same as the current AppEngine system, but pricier.
ReplyDelete:D
ReplyDelete<3 goog
Agree with Peter: SSL on custom domains is a must in the regular App Engine apps!
ReplyDeleteLooks very interesting but are you guys going to sort out the full text search story at least for this "for business" version? That is the biggest show stopper for me and my company right now and I do not think we are the only ones struggling with this.
ReplyDeleteGreat News..
ReplyDeleteSQL Support was what a business user need most.
A few questions:
1. What about 30 second time limit? Are you people going to increase it ?
2. Your SQL would resembles to which SQL server in market? MS SQL Server? MySQL??
3. Can we expect Threading and socket communication support?
interesting!
ReplyDeleteGood news and very excited about the SQL support :-)
ReplyDeleteAdSense - which is responsible for more than 90% of Google's revenue - does not even have a phone number! Nor an email address (it auto-rejects you to go to the forums)! And the forums aren't even monitored by a Google employee!
ReplyDeleteThe Nexus One was released without ANY support whatsoever!
I don't think the old Goog has enough experience with support, or respect for it - especially enterprise class support - to take this to serious heights.
Only time will tell. But after trying for seven months to solve a simple AdSense problem that would have taken 2 mins over the phone - I certainly won't be the first guinea pig.
+1 on Manjoor's comment. These two constraints are my biggest source of headaches with GAE. The 30 second limit, coupled with the horrible performance of JDO, forced me to rewrite a good chunk of my app using the native API. The lack of SQL forced me to sync to an external MySQL database for reporting capabilities. Not having to do both would have cut at least 20% of the sum development time.
ReplyDeleteCould you share a bit more detail about the "dedicated full-featured SQL servers" coming in Q3? Is it going to be an existing (OS?) database engine, something home-grown, or ...?
ReplyDeleteThis comment has been removed by a blog administrator.
ReplyDeleteHey dude, Google and Adsense go together. They together come out with the best business over the net.
ReplyDeleteWaiting for SQL support...
ReplyDelete