EBS: All content tagged as EBS in NoSQL databases and polyglot persistence
The Amazon team released a whitepaper comparing the total cost of ownership for 3 scenarios:
- on-premise NoSQL database
- NoSQL database deployed on Amazon EC2 and Amazon EBS
- Amazon DynamoDB
As you can imagine DynamoDB comes out as the most cost-effective solution (79% more effective than on-premise NoSQL database and 61% more cost-effective than AWS hosted NoSQL database). Read or download the paper after the break.
The topic of running MongoDB on Amazon Web Services using Elastic Block Storage came up again among the 10 tips for running MongoDB from Engine Yard:
you should know that the performance of Amazon’s Elastic Block Storage (EBS) can be inconsistent.
Following up on that Mahesh P-Subramanya aptly added:
Indeed! I’d actually take it a step further and say Do not use EBS in any environment where reliability and/or performance characteristics of your disk-access are important. Or, to put it differently, asynchronous backups - OK, disk-based databases - Not So Much.
Interestingly though, some presentations earlier this year–MongoDB in the Amazon Cloud and Running MongoDB on the Cloud—left me, and others with the impression that EBS should not be dismissed so fast.
Original title and link: MongoDB and Amazon Elastic Block Storage (EBS) ( ©myNoSQL)
The only thing I dislike about that EC2 guide is that it’s suggesting to use EBS instead of the regular EC2 instance storage
This is an apt question in the light of the prolongued Amazon outage, Reddit’s experience with EBS, the unpredictable EBS performance, and Netflix’s Adrian Cockcroft explanation of multi-tenancy impact on the Amazon EBS performance. Maybe someone could answer it.
Original title and link: MongoDB and Amazon: Why EBS? ( ©myNoSQL)
A discussion on the MongoDB group about EBS snapshot backups of journaled MongoDB reminded me of a Jared Rosoff’s slides “MongoDB on EC2 and EBS” covering many important aspects of running MongoDB on the Amazon cloud:
MongoDB components and their requirements
deployment options and corresponding Amazon EC2 instance types
operating systems, specific configurations, and operational advise:
- deployment automation
- backups and restoration
- 3-node replica set
- 2-nodes + arbiter
- multi-datacenter (availability zone) 3-node replica set
- sharded MongoDB
While tempting, running databases in the cloud is not as simple as Amazon makes it sound. Reddit felt that with their Cassandra and PostgreSQL deployment.