4 ms·

I'm waiting for the first hosting company to offer a drop-in replacement for AppEngine. It should be easy to compete on support with Google, and there are tons

by koenbok 16y ago

I'm waiting for the first hosting company to offer a drop-in replacement for AppEngine. It should be easy to compete on support with Google, and there are tons of AppEngine applications out there that can turn into big successes.

sidmitra 16y ago
The appengine to me 'personally' has always felt too restrictive and suitable for pet projects than full scale apps. But then again, i might be stuck in a "relational" mindset.
- koenbok 16y ago
  Maybe, maybe not. We just wrote a big app (enstore.com) on top of it without too much problems. It's another way of thinking, but I actually started to like a restrictive datastore with very consistent characteristics. Now if they only can get it up to speed again (http://bit.ly/as4sij http://bit.ly/as4sij) :-)
  - iampims 16y ago
    Enstore is running on Django, right? Did you run into any gae specific issues?
axiom 16y ago
That's a seriously phenomenal idea. Just by charging for the service and using a SQL database they could avoid 90% of the problems GAE has experienced. I would pay $1000/month without a second thought to have a quick migration away from GAE, and no doubt a lot of other people would as well.
- bretthoerner 16y ago
  How would quick migration work from BigTable to SQL? And which language do you use (on AppEngine), out of curiosity?
  - sidmitra 16y ago
    My guess is a migration from key value(or most NoSQL) to relational would be an easier path, right?
  - axiom 16y ago
    We're using Python with Django. AppScale (similar project as TyphoonAE but a bit more mature) has done a decent job of writing a layer that implements all datastore functionality on top of variety of databases (some SQL, some not.) It's not too tricky actually since in most ways the App Engine datastore interface is a subset of SQL (kind if like SQL without joins actually.)

4 ms·

I'm waiting for the first hosting company to offer a drop-in replacement for AppEngine. It should be easy to compete on support with Google, and there are tons

by koenbok 16y ago

sidmitra 16y ago
The appengine to me 'personally' has always felt too restrictive and suitable for pet projects than full scale apps. But then again, i might be stuck in a "relational" mindset.
- koenbok 16y ago
  Maybe, maybe not. We just wrote a big app (enstore.com) on top of it without too much problems. It's another way of thinking, but I actually started to like a restrictive datastore with very consistent characteristics. Now if they only can get it up to speed again (http://bit.ly/as4sij http://bit.ly/as4sij) :-)
  - iampims 16y ago
    Enstore is running on Django, right? Did you run into any gae specific issues?
axiom 16y ago
That's a seriously phenomenal idea. Just by charging for the service and using a SQL database they could avoid 90% of the problems GAE has experienced. I would pay $1000/month without a second thought to have a quick migration away from GAE, and no doubt a lot of other people would as well.
- bretthoerner 16y ago
  How would quick migration work from BigTable to SQL? And which language do you use (on AppEngine), out of curiosity?
  - sidmitra 16y ago
    My guess is a migration from key value(or most NoSQL) to relational would be an easier path, right?
  - axiom 16y ago
    We're using Python with Django. AppScale (similar project as TyphoonAE but a bit more mature) has done a decent job of writing a layer that implements all datastore functionality on top of variety of databases (some SQL, some not.) It's not too tricky actually since in most ways the App Engine datastore interface is a subset of SQL (kind if like SQL without joins actually.)