Showing posts with label Cloud Service comparison: Google App Engine vs. Joyent. Show all posts
Showing posts with label Cloud Service comparison: Google App Engine vs. Joyent. Show all posts

Friday, June 13, 2008

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

Although, it must be pointed out, that each of the "hardware as a
service" vendor have their own limitations in terms of OSes and/or
server stack images that can be used. To provide a generic service,
some sacrifices must be made for flexibility. This has always been
true for software frameworks and even languages (try using Ruby on
Rails for a time critical embedded system), but we are now seeing it
when it comes to "operating systems for the cloud".

Frankly, I'd rather have the OS dependency than the language
dependency, unless the framework provided met my needs exactly. Then,
I'd take the framework any day, as it hides more of the operational
issues that I just wouldn't care about.

James

On Jun 12, 2:26 pm, randall <rand...@qrimp.com> wrote:
> Just to be clear, Facebook is not using Joyent, rather the vendors of
> apps that run within Facebook are using Joyent. I'm sure part of the
> popularity is just due to the fact that Joyent has been around a lot
> longer than AppEngine.
>
> The language issue isn't superficial in my opinion. AppEngine
> customers face vendor lock in on a significant scale because the
> entire AppEngine platform is proprietary with bigtable, mapreduce,
> etc. Joyent, Mosso and others don't suffer his vendor lock in, because
> they support more standard environments like relational databases and
> an array of programming languages.
>
> On top of that, you have the Googlenoia and growing impression of
> Google as the company putting smaller application providers out of
> business, replacing Microsoft as the company everyone loves to hate.
>
> - randall
>
> On Jun 12, 3:05 pm, "Michael Moran" <professor.mo...@gmail.com> 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
-~----------~----~----~----~------~----~------~--~---

Thursday, June 12, 2008

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

Just to be clear, Facebook is not using Joyent, rather the vendors of
apps that run within Facebook are using Joyent. I'm sure part of the
popularity is just due to the fact that Joyent has been around a lot
longer than AppEngine.

The language issue isn't superficial in my opinion. AppEngine
customers face vendor lock in on a significant scale because the
entire AppEngine platform is proprietary with bigtable, mapreduce,
etc. Joyent, Mosso and others don't suffer his vendor lock in, because
they support more standard environments like relational databases and
an array of programming languages.

On top of that, you have the Googlenoia and growing impression of
Google as the company putting smaller application providers out of
business, replacing Microsoft as the company everyone loves to hate.

- randall

On Jun 12, 3:05 pm, "Michael Moran" <profes.....@gmail.com> 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
-~----------~----~----~----~------~----~------~--~---

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

The biggest reason I see that Joyent is a leader in facebook app hosting is becaue Joyent offers a true virtual machine set up preconfigured to run PHP, Rails, and Python. You can get root access and run shell scripts. It’s setup to scale out based on demand. (Question to self: I wonder how they scale the database part). Another huge plus is that Joyent is peered with Facebook’s network…thus eliminating any bandwidth costs. Also, the first year is free.

Google’s app engine on the other hand is a container for python/django apps. No shell access. But they handle all the scaling issues. Also, you might run out of bandwidth pretty quickly if it’s a successful app and google app engine is only in preview mode with limited bandwidth available.

Ben

http://servicecloud.com

http://bencherian.com

From: cloud-computing@googlegroups.com [mailto:cloud-computing@googlegroups.com] On Behalf Of Michael Moran
Sent: Thursday, June 12, 2008 4:06 PM
To: cloud-computing@googlegroups.com
Subject: Cloud Service comparison: Google App Engine vs. Joyent

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
-~----------~----~----~----~------~----~------~--~---

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
-~----------~----~----~----~------~----~------~--~---

Cloud Service comparison: Google App Engine vs. Joyent

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
-~----------~----~----~----~------~----~------~--~---