9 Comments »Yesterday, most of the buzz floating around was about Google’s new App Engine. The service has been hailed as the competitor to S3 but both Nate Westheimer and David Recordon say that the true competitor is Facebook. Nate says that the real problem with the new App Engine in comparison to S3 & EC2 is all the contraints. Right now all apps must be written in python and should integrate with the Google infrastructure. Trying to combine statements of Nate & David is somewhat complex since they have presented their arguments in different manners.
Both make accurate points. While the Google App Engine leverages Google’s userbase, it doesn’t store anything pertaining to relationships. It let’s the social networks handle that function. Just as Facebook has an application directory, so does the App Engine. The main point is that Google has created a central location for you to host an application and gain users. One downfall is you can’t compare the size of each application’s userbase but I would imagine the opportunity is relatively substantial.
While on a technical and theoretical level Google App Engine is a competitor to Facebook, on a basic level it definitely isn’t. What average user of Google is going to navigate to the Google App Engine application directory? Aside from free hosting, do developers have much of an incentive to build on this new platform? The discussion of Google App Engine being a competitor to Facebook makes sense but is unfounded because the average person is not going to be interfacing with this new application platform. What do you think? Do you even care about the Google App engine?
In my opinion, a social network is essential for any web application. You may grow your own social network for your web app, but I don't think people like to build their social graph over and over again. And so Google probably will add social networking to its App Engine, e.g. via Orkut. Then it is a Facebook competitor.
In my opinion, a social network is essential for any web application. You may grow your own social network for your web app, but I don’t think people like to build their social graph over and over again. And so Google probably will add social networking to its App Engine, e.g. via Orkut. Then it is a Facebook competitor.
Are you serious? Google App Engine is Huge. And it doesn't really compete with facebook at all.
App Engine and S3 are options for hosting a distributed application on a 'cloud', taking away the details of running a bunch of servers yourself.
App Engine gives an incredibly easy way to write and deploy an application that can scale to millions of users in no more time than it takes them to propagate it across their network (minutes? hours?) No design headaches, no complex master/slave database failover setups with memcached servers and the rest of it. No headaches managing the fundamental disconnect between an object-oriented data model and a bunch of relational tables. And all in plain, open-source python. Write it and push it out to the world in 10 minutes.
I won't be at all surprised if open source packages come out soon that mimic App Engine's API, since that's almost certainly a good model to design to for scalability. Other services may crop up to compete with App Engine, so that the app you write could be dropped into any or all of them.
App Engine basically lets you handle http requests and use a data store. If you need more control over the architecture than what Google's easy offering gives you (say, heavy backend data crunching) then you should look at EC2. They give you root on all of the machines you care to buy time on, and you can easily shrink or grow your cluster. It's not as easy though, since it's up to you to administer the machines. It's different enough from App Engine that in most situations there is probably an obvious answer as to which is better for the job.
For an easier time on S3, there are also of course a whole bunch of startups that build a service that runs on S3 and then offer their users something easier. Just to pick one example, heroku.com lets your write a ruby on rails app right inside your browser and then deploy it in S3. Pretty sweet.
I don't understand why App Engine would be considered a threat to the facebook platform. You don't host an app inside facebook platform, you host it outside and communicate using standard web protocols. If anything, App Engine provides a new, easy way to write and deploy a facebook application that won't have any trouble scaling to facebook's entire user base, should it catch on. That's good for both platforms.
Yes, you can tie an App Engine app to Google accounts, but that's optional. You could use OpenID instead of Google accounts for an App Engine app. You just need to include the code to do it (hopefully a library will make that dead simple).
Are you serious? Google App Engine is Huge. And it doesn’t really compete with facebook at all.
App Engine and S3 are options for hosting a distributed application on a ‘cloud’, taking away the details of running a bunch of servers yourself.
App Engine gives an incredibly easy way to write and deploy an application that can scale to millions of users in no more time than it takes them to propagate it across their network (minutes? hours?) No design headaches, no complex master/slave database failover setups with memcached servers and the rest of it. No headaches managing the fundamental disconnect between an object-oriented data model and a bunch of relational tables. And all in plain, open-source python. Write it and push it out to the world in 10 minutes.
I won’t be at all surprised if open source packages come out soon that mimic App Engine’s API, since that’s almost certainly a good model to design to for scalability. Other services may crop up to compete with App Engine, so that the app you write could be dropped into any or all of them.
App Engine basically lets you handle http requests and use a data store. If you need more control over the architecture than what Google’s easy offering gives you (say, heavy backend data crunching) then you should look at EC2. They give you root on all of the machines you care to buy time on, and you can easily shrink or grow your cluster. It’s not as easy though, since it’s up to you to administer the machines. It’s different enough from App Engine that in most situations there is probably an obvious answer as to which is better for the job.
For an easier time on S3, there are also of course a whole bunch of startups that build a service that runs on S3 and then offer their users something easier. Just to pick one example, heroku.com lets your write a ruby on rails app right inside your browser and then deploy it in S3. Pretty sweet.
I don’t understand why App Engine would be considered a threat to the facebook platform. You don’t host an app inside facebook platform, you host it outside and communicate using standard web protocols. If anything, App Engine provides a new, easy way to write and deploy a facebook application that won’t have any trouble scaling to facebook’s entire user base, should it catch on. That’s good for both platforms.
Yes, you can tie an App Engine app to Google accounts, but that’s optional. You could use OpenID instead of Google accounts for an App Engine app. You just need to include the code to do it (hopefully a library will make that dead simple).
A social network is just a set of associations between users. Google doesn't need to 'add' anything special to App Engine to create that capability. Any application with its own data store can store any associations it likes, between any pair of objects it likes.
App Engine is a hosting platform for developers. Why would it need its own social network? It can tie into all of the social networks that already exist. Orkut already has its own api, just like all the rest of the OpenSocial containers. If you want to build an Orkut application in App Engine, you can include a python Orkut library to ease the task.
The only thing Google could do to make this even easier would be to bundle an Orkut library into the standard App Engine API like they do for the Google Accounts.
A social network is just a set of associations between users. Google doesn’t need to ‘add’ anything special to App Engine to create that capability. Any application with its own data store can store any associations it likes, between any pair of objects it likes.
App Engine is a hosting platform for developers. Why would it need its own social network? It can tie into all of the social networks that already exist. Orkut already has its own api, just like all the rest of the OpenSocial containers. If you want to build an Orkut application in App Engine, you can include a python Orkut library to ease the task.
The only thing Google could do to make this even easier would be to bundle an Orkut library into the standard App Engine API like they do for the Google Accounts.
Replace “add” with “bundle” in my comment and it's the same statement like yours. App Engine plus Orkut (or any open social network) makes implementing a social app easier and the user can share the app's functionality with his existing friends.
Replace “add” with “bundle” in my comment and it’s the same statement like yours. App Engine plus Orkut (or any open social network) makes implementing a social app easier and the user can share the app’s functionality with his existing friends.
Thanks for sharing.
Logan
http://xtupload.com