Hot answers tagged google-app-engine
There probably is a performance difference, but it's probably pretty small. Here's what I found (all based on the the Google Docs for Python). BigTable does not support PolyModel information natively. Instead, it's implemented using a 'class' property. So, when you try to perform a search, for example, to find a base class, you will be searching on this ...
I'm also working with the GAE datastore right now, you should check this article if you haven't already. If you have found something useful, please update your question. EDIT: I found this today, check it out.
Both Microsoft and Amazon offer SQL databases in the cloud. GAE isn't an RDBMS, it's NoSQL in the cloud. If you just need an object data store, well someone has probably written a wrapper in the language you want, otherwise there's Python and Java. If you need an RDBMS, I suggest you check out either Microsoft's SQL Azure or Amazon's Amazon RDS.
Roughly speaking, no. The big demand of GAE is the integrated, scalable, cloud backend. Without the backend hardware, it's functionally Django on bigtables. If the customers (quite rightly) don't like vendor lockin, GAE is not for them. What features of GAE would you keep, if not for the backend?
I think approcket can help you. It syncs data from GAE datastore to mysql. Is this what you ask for?
This msdn walkthrough should have everything you need to accomplish what you want to do on the SSRS 2005 side. Pay attention to the section on setting up for remote smtp. Especially the part about setting SendUsing to 2. This google guide provides the steps to configure things on their end. The setup for SSRS 2008 isn't much different.
It seems to me your problem is that you are trying to test performance metrics that are not well supported in the underlying db. This makes it very difficult to compare performance across systems because the underlying approaches are very different. I don't think it is possible to do apples to apples comparisons just as I don't think you can do an apples ...
Your second approach seem to be the best. Having a Message entity with key relations to sender/reciever. As for you deleting a user dilema, you should consider not removing the entity when a user is deleted as this would break your db consistency. You should probably just have a logic deletion (eg a boolean value changed when a user is deleted), that way, ...
Only top voted, non community-wiki answers of a minimum length are eligible