Trust me ... a significant amount of engineering hours has been put into
the GAE branch, both pre (when Vince did his original port) and again by
me when I merged it into the main branch.
But for all of Google's hype, there are major short comings with it. My
biggest concern, which is being realized now, is vendor lock in. At
this precise moment, due to a bug __THEY__ introduced, we are
completely left out in the cold until they fix it. They have no SLA.
The bug has been outstanding for 2weeks now, acknowledged by Google, yet
no fix.
How many businesses could afford to go offline for 2weeks at least with
no real end in sight?
This is why i fear the likes of Google App Engine, Microsoft Azure,
SalesForce Force.com -- they all suffer the same fate. Use them at
your own risk.
We are living proof of what happens when clouds go bad
At least with Amazon/Rackspace/GoGrid you can easily move between the
vendors. Assuming of course you aren't stupid enough to lock yourself
into Amazon's feature-set too much. It is vitally important you keep a
level of abstraction, to give yourself options when the lights go out
for whatever reason.
Peter Farrell wrote:
I would really like to the see the GAE version move forward. Enlist
is one app that is unique and would do really well being publically
available on GAE. What can I do to help or encourage further dev?
--
official tag/function reference: http://openbd.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
