nosql.mypopescu.commyNoSQL • NoSQL Databases and Polyglot Persistence: A Curated Guide

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 BigData Hadoop Case Studies Column stores Document databases Key-Value stores Graph databases NoSQL Events Close Explore all topics Hadoop BigData MongoDB Redis Cassandra HBase Riak CouchDB Neo4j MapReduce myNoSQL myNoSQL NoSQL Databases and Polyglot Persistence: A Curated Guide Home NoSQL?!? What is NoSQL? Why NoSQL? All NoSQL databases Getting started NoSQL Guides,NoSQL tutorials, NoSQL books, NoSQL papers Powered by NoSQL NoSQL Libraries NoSQL conferences Monday, 24 November 2014 Autoscaling, welcome to Google Compute Engine About: distributed systems , scalability , Autoscaling allows customers to build more cost effective and resilient applications. Using Compute Engine Autoscaling, you can ensure that exactly the right number of Compute Engine instances are available at any given time to handle your application’s workload. This saves you money when your application’s usage is low, and ensures your application is responsive when utilization is high. Autoscaling is the the Holy grail of a distributed system. The promise is that the system is be able to adapt—both up and down—to the needs/requirements/SLAs. Basically, the system will be able to get the performance it is demanded to provide, maximum availability, and these with optimal costs. The first step in finding this Holy grail is to be able to describe the needs and requirements and SLAs of the system. Original title and link: Autoscaling, welcome to Google Compute Engine ( NoSQL database ©myNoSQL) via: http://googlecloudplatform.blogspot.com/2014/11/autoscaling-welcome-to-google-compute.html Most Popular Articles Translate SQL to MongoDB MapReduce Tutorial: Getting Started With Cassandra CouchDB vs MongoDB: An attempt for a More Informed Comparison Cassandra @ Twitter: An Interview with Ryan King A Couple of Nice GUI Tools for MongoDB NoSQL benchmarks and performance evaluations Ehcache: Distributed Cache or NoSQL Store? Document Databases Compared: CouchDB, MongoDB, RavenDB Quick Review of Existing Graph Databases NoSQL Data ModelingPage 1Older posts › by Alex Popescu & Ana-Maria Bacalu Patronage Most read Comments Big Data Hadoop MapReduce Cassandra HBase CouchDB MongoDB Redis Riak Neo4j Subscribe to my RSS feed About Contact Search Copyright © 2009-2015. All rights reserved. This blog is called myNoSQL and it is written by me, Alex Popescu, a software architect with a passion for open source and communities. It records my readings, learnings, and opinions on NoSQL databases, polyglot persistence, and distributed systemssubjects that I’m passionate about. The opinions expressed here are my own, and no other party necessarily agrees with them . If you feel I’m biased, I probably am. Tumblr theme by Alex Popescu Bistrian...