thanks a lot for all the comments.  i think one comment sums it up
beautifully: "Neither Google nor Amazon are idiots" so both have their good
and bad points.  i think we will go with gae for the prototype but keep the
datastore bits separated just in case the need to switch to ec2 in the
future.

On Fri, Sep 25, 2009 at 1:56 PM, OvermindDL1 <overmind...@gmail.com> wrote:

>
> On Thu, Sep 24, 2009 at 11:49 PM, Robin B <robi...@gmail.com> wrote:
> >
> > That's interesting you mention Erlang: I was working on building an
> > Erlang based App Cluster around the time when AppEngine was announced/
> > released.  You can achieve a much higher handlers/cpu or handlers/
> > memory density using Erlang because each handler is a green thread
> > with cheap context switching, each handler/process costs as little as
> > 200 bytes of system memory, and system libraries can loaded once into
> > memory and shared between all apps because Erlang is a functional
> > programming language.  The thing that made me trade Erlang for
> > AppEngine was having access to BigTable.
> >
> > AppEngine has numerous features (simple deployment, load balancing,
> > dynamic scalability), but the main benefit is access to a scalable
> > database; BigTable provides seamless multi-master database writes.  If
> > a developer has never considered the challenges of scaling database
> > write throughput, then they would not realize how much time AppEngine
> > will save them in designing and hosting a truly scalable web
> > application.
>
> It would not be hard to add BigTable into Erlang though, Erlang is not
> that hard to bind to after all.  The Mnasia database built into Erlang
> though is fully distributed and fault tolerant and things can be made
> to exist on disk or in memory only for speed and all sorts of things,
> it is actually quite powerful, just a bit slower then normal SQL
> servers of course, due to the distributed nature.  Erlang also has
> load balancing, dynamic scalability, and the deployment when using the
> Erlang webserver Yaws is quite simple, it is fully ready to handle
> just about everything you could ever throw at it, you just need a few
> computers to load it on first.  :)
>
> I prefer Python as a programming language (although I would still use
> Erlang if AppEngine ever supports it, it is just an awesome language).
>  I am using AppEngine because other people requested I did, been
> learning it.  :)
>
> >
>


-- 
.......__o
.......\<,
....( )/ ( )...

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

Reply via email to