Re: Cloud Service comparison: Google App Engine vs. Joyent

GAE is appropriate for a two tier system (client and database) or a
system where everything you need can be provided by an external service.
This is because GAE provides a very simple and limited development
environment that is designed to scale websites, not backend services.

Joyent et all provide a general backend computing framework in which you
can create your own services according to any architecture you want. If
you want to create a media transcoding service in GAE, for example, you
couldn't. You are very limited in the amount of CPU you can use at one
time, you are limited in the number of amount of files you can store,
and there's no way for your application to get CPU to control the
transcoding process. SmugMug wrote up a nice overview
(http://blogs.smugmug.com/don/2008/06/03/skynet-lives-aka-ec2-smugmug/)
of a similar process that couldn't be built on GAE.

Michael Moran wrote:
> According to the "Cloud Computing" entry in Wikipedia, it states
> that "Currently 25% of Facebook daily active application usage runs on
> Joyent."
> Can anyone provide reasons why Facebook uses Joyent instead of, say,
> Google App Engine?
> Also, in more general terms, can anyone provide examples where Joyent
> would be better than Google App Engine, or vice-versa?
> Superficially, it appears the main difference, from a developers point
> of view, is that Joyent offers wider language support than Google's
> App Engine (python only).
>
> Thank you very much,
>
> --Michael
> Miami, FL
>
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cloud Computing" group.
To post to this group, send email to cloud-computing@googlegroups.com
To unsubscribe from this group, send email to cloud-computing-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.ca/group/cloud-computing?hl=en
-~----------~----~----~----~------~----~------~--~---