ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

appengine: All content tagged as appengine in NoSQL databases and polyglot persistence

Google App Engine High Replication Datastore

The High Replication Datastore provides the highest level of availability for your reads and writes, at the cost of increased latency for writes and changes in consistency guarantees in the API. The High Replication Datastore increases the number of data centers that maintain replicas of your data by using the Paxos algorithm to synchronize that data across datacenters in real time.

Still not completely decentralized a la Amazon Dynamo.

Original title and link: Google App Engine High Replication Datastore (NoSQL databases © myNoSQL)

via: http://googleappengine.blogspot.com/2011/01/announcing-high-replication-datastore.html


Goodbye Google App Engine (GAE)

[…] developing on GAE introduced such a design complexity that working around it pushes us 5 months behind schedule. Now that we had developed tools and workarounds for all the problems we found in GAE, we were starting being fast with the development of features eventually, and at that point we found the cloud was totally unstable, doggy.

Carlos Ble’s post lists 13 issues they’ve had with Google App Engine. Now, I know Google App Engine is not offering the best experience or performance, has a couple of (interesting?) constraints and Google support is (how to put it gently?) completely missing, but some of the points listed in there make me think they’ve thrown themselves in heads first without trying to understand:

  • what kind of persistency is Google App Engine offering
  • how to model and access your data in Google App Engine
  • data migration paths
  • architecting with SLAs in mind

These should sound kind of familiar to everyone building distributed systems using NoSQL databases. Going live after prototyping a “Hello world” with a NoSQL database will not gonna “scale” :-).

Original title and link: Goodbye Google App Engine (GAE) (NoSQL databases © myNoSQL)

via: http://www.carlosble.com/?p=719


Grails and NoSQL

Grails is probably one of the most flexible and productive frameworks that runs on the Java VM. One of the most appreciated aspects of Grails is its object relational mapping known as GORM, but lately I have also noticed some NoSQL plugins that I’m listing here (note: please let me know if I’ve missed any):

Unfortunately it was difficult to figure out the status of these plugins only based on their extremely scarce documentation pages. Anyway I really hope to see more activity in this direction as this would definitely help with NoSQL adoption in the more “enterprisey” world.