By the way, if hope to get additional help anywhere, you should give a concise set of reasoning as to why Parse and Google App Engine don't fit the use case you're looking for, as all of the articles you seem to consider as proving this service do so in a nosql based way based on a mostly REST API, GAE and Parse work similarly enough to that that the differences don't really matter..
kris On Wed, Aug 22, 2012 at 11:24 AM, Kristopher Micinski <[email protected]> wrote: > Well, in general I think people dislike buzzwords more than anything. > "X as a service," can literally mean anything to any set of developers > that are willing to push the concept to back their company's newest > concept, shelling out a few grand to promote their piece of redundant > crap with a conference. > > In general what confuses me about your question is that you seem to be > more stuck on the buzzword than the end goal. Parse and Google App > Engine. > > I'm also pretty skeptical that you can brush my answer off so quickly > when services I've mentioned are *included in the article you linked*! > :-) > > Moreover, Parse offers a NoSQL based solution, same as any of the > people in this article, and AWS is another option. > > Why would the Google developers have any opinion on this? If you > check the history of the group you'll find that none of the Google > devs have ever endorsed a non Google product / backend, if they said > anything it would probably be to point you at a list of the same > things I did or point you at Google App Engine. > > But the more underlying factor is that, you're talking about wanting a > "database as a service," when what you really *should* be talking > about is the end use of that service in your app. The reason people > have web backends is the same as any distributed system: replication, > (partial) consistency, and persistence. What's more important is that > what you can do with your *app*, the problems you face with > implementing a distributed system the proper way across the landscape > of installations of your app will vary much more than the minor choice > of which backend provider to use. > > By the way, assuming this is the use case for your app, you might also > look into cloud to device messaging, which sort of solves the problem > of polling these databases.. > > I don't think it's that I misunderstood, but you seem to be brushing > off real answers to your question in favor of solutions with the > buzzword "database as a service" tied to them, frequent of the mid > level managers you see in software companies :-) ... > > kris > > On Wed, Aug 22, 2012 at 11:12 AM, Mark Liversedge <[email protected]> > wrote: >> I have no problems. Database as a service is a relatively new concept. This >> article was useful >> http://www.readwriteweb.com/cloud/2011/01/7-cloud-based-database-service.php >> >> I was hoping some of the devs here could share experiences of them, but I >> guess this is more of a coding forum. Not that there is anything wrong with >> that. >> >> I'm always open to advice. But was perhaps a little terse. The article you >> linked to didn't seem relevant and you didn't appear to have understood my >> question. >> >> But thanks anyway! >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
