high_scalability high_scalability-2009 high_scalability-2009-736 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: With so many database options available these days, like for the rest of life, it's natural to wonder how it all fits together . Amazon complicated, or rather expanded the available options by introducing RDS, their relational database service . RDS is MySQL safely cocooned as a manageable cloud element, resting boldly within an energy providing elastic CPU pool , supported by a virtually infinite supply of very capable virtualized storage . MySQL in AWS is now easy to start, stop, monitor, backup, snapshot, expand, and effortlessly move up and down the instance hierarchy. What it's not, contrary to what you might expect, is a scale-out solution, it's a scale-up solution. You get more by buying a bigger instance, not by horizontally adding more instances. There's a limit . Admittedly a larger limit now with Amazon's new high memory instances . That's OK, well maybe not for people who helped grow Amazon's ecosystem by offering a similar product, but so many projects use M
sentIndex sentText sentNum sentScore
1 With so many database options available these days, like for the rest of life, it's natural to wonder how it all fits together . [sent-1, score-0.351]
2 Amazon complicated, or rather expanded the available options by introducing RDS, their relational database service . [sent-2, score-0.212]
3 RDS is MySQL safely cocooned as a manageable cloud element, resting boldly within an energy providing elastic CPU pool , supported by a virtually infinite supply of very capable virtualized storage . [sent-3, score-0.168]
4 MySQL in AWS is now easy to start, stop, monitor, backup, snapshot, expand, and effortlessly move up and down the instance hierarchy. [sent-4, score-0.094]
5 What it's not, contrary to what you might expect, is a scale-out solution, it's a scale-up solution. [sent-5, score-0.09]
6 That's OK, well maybe not for people who helped grow Amazon's ecosystem by offering a similar product, but so many projects use MySQL that this is a big win for a lot of people. [sent-9, score-0.087]
7 It makes life easier even if the promise of infinite relational database storage has yet to be realized. [sent-10, score-0.208]
8 If one of the reasons you were considering using a Platform as a Service is to knock the database item off your worry list, RDS is one more reason to consider playing your own general contractor and orchestrating all the elements together yourself. [sent-11, score-0.322]
9 As more services become packaged into cloud capable components this is likely how many systems will be bolted together in the future. [sent-12, score-0.2]
10 But we are left wondering, how RDS fits together with SimpleDB and all the other database options? [sent-13, score-0.219]
11 As an organizing principle James came up with this taxonomy for databases based on what the customer wants to do, their intent: features-first - This is the relation database bucket where the database provides a lot of high level features that make the programmer's job a lot easier. [sent-15, score-0.874]
12 They generally lack features and put a lot more responsibility back on the programmer. [sent-19, score-0.181]
13 They generally don't have the features or scalability of other systems. [sent-22, score-0.094]
14 I'm not sure where a graph database like Neo4j would fit in the list, but James has created a useful way to look at things and of course he provides a lot more detail in his post . [sent-26, score-0.299]
15 So all you have to do is figure out your intention, find out where you are belong in the list, and make a choice :-) I know, you want it all, you deserve it all, but that doesn't seem to be happening. [sent-27, score-0.193]
16 Sites for a very long time will be forged from a mix of technologies and we are the master mixoligists. [sent-28, score-0.115]
17 A nice NoSQL taxonomy: key‐value‐cache, key‐value‐store, eventually‐consistent key‐value‐store, ordered‐key‐value‐store, data‐structures server, tuple‐store, object database, document store, wide columnar store. [sent-30, score-0.082]
wordName wordTfidf (topN-words)
[('rds', 0.249), ('ringo', 0.207), ('taxonomy', 0.207), ('examples', 0.184), ('james', 0.169), ('store', 0.166), ('value', 0.142), ('simpledb', 0.137), ('options', 0.132), ('database', 0.127), ('boldly', 0.115), ('forged', 0.115), ('isnow', 0.115), ('newhigh', 0.115), ('resting', 0.115), ('admittedly', 0.108), ('kai', 0.108), ('bolted', 0.108), ('berkelydb', 0.103), ('deserve', 0.103), ('orchestrating', 0.103), ('thrudb', 0.103), ('dynomite', 0.103), ('netezza', 0.103), ('list', 0.101), ('intent', 0.1), ('key', 0.095), ('generally', 0.094), ('tuple', 0.094), ('effortlessly', 0.094), ('together', 0.092), ('belong', 0.09), ('pnuts', 0.09), ('contrary', 0.09), ('manageable', 0.088), ('lot', 0.087), ('vertica', 0.086), ('expanded', 0.085), ('aster', 0.085), ('intention', 0.085), ('fit', 0.085), ('hypertable', 0.083), ('relation', 0.082), ('columnar', 0.082), ('life', 0.081), ('safely', 0.08), ('organizing', 0.079), ('cassandra', 0.078), ('bucket', 0.078), ('voldemort', 0.077)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999982 736 high scalability-2009-11-04-Damn, Which Database do I Use Now?
Introduction: With so many database options available these days, like for the rest of life, it's natural to wonder how it all fits together . Amazon complicated, or rather expanded the available options by introducing RDS, their relational database service . RDS is MySQL safely cocooned as a manageable cloud element, resting boldly within an energy providing elastic CPU pool , supported by a virtually infinite supply of very capable virtualized storage . MySQL in AWS is now easy to start, stop, monitor, backup, snapshot, expand, and effortlessly move up and down the instance hierarchy. What it's not, contrary to what you might expect, is a scale-out solution, it's a scale-up solution. You get more by buying a bigger instance, not by horizontally adding more instances. There's a limit . Admittedly a larger limit now with Amazon's new high memory instances . That's OK, well maybe not for people who helped grow Amazon's ecosystem by offering a similar product, but so many projects use M
2 0.19810896 737 high scalability-2009-11-05-A Yes for a NoSQL Taxonomy
Introduction: NorthScale's Steven Yen in his highly entertaining NoSQL is a Horseless Carriage presentation has come up with a NoSQL taxonomy that thankfully focuses a little more on what NoSQL is, than what it isn't : key‐value‐cache memcached, repcached, coherence, infinispan, eXtreme scale, jboss cache, velocity, terracoqa key‐value‐store keyspace, flare, schema‐free, RAMCloud eventually‐consistent key‐value‐store dynamo, voldemort, Dynomite, SubRecord, Mo8onDb, Dovetaildb ordered‐key‐value‐store tokyo tyrant, lightcloud, NMDB, luxio, memcachedb, actord data‐structures server redis tuple‐store gigaspaces, coord, apache river object database ZopeDB, db4o, Shoal document store CouchDB, Mongo, Jackrabbit, XML Databases, ThruDB, CloudKit, Perservere, Riak Basho, Scalaris wide columnar store BigTable, Hbase, Cassandra, Hypertable, KAI, OpenNeptune, Qbase, KDI "Who will win?"
3 0.17930841 925 high scalability-2010-10-22-Paper: Netflix’s Transition to High-Availability Storage Systems
Introduction: In an audacious move for such an established property, Netflix is moving their website out of the comfort of their own datacenter and into the wilds of the Amazon cloud. This paper by Netflix's Siddharth “Sid” Anand, Netflix’s Transition to High-Availability Storage Systems , gives a detailed look at this transition and does a deep dive on SimpleDB best practices, focussing especially on techniques useful to those who are making the move from a RDBMS. Sid is going to give a talk at QCon based on this paper and he would appreciate your feedback. So if you have any comments or thoughts please comment here or email Sid at r39132@hotmail.com or Twitter at @r39132 Here's the introduction from the paper: Circa late 2008, Netflix had a single data center. This single data center raised a few concerns. As a single-point-of-failure (a.k.a. SPOF), it represented a liability – data center outages meant interruptions to service and negative customer impact. Additionally, with growth in both
4 0.17685869 670 high scalability-2009-08-05-Anti-RDBMS: A list of distributed key-value stores
Introduction: Update 8: Introducing MongoDB by Eliot Horowit . Update 7: The Future of Scalable Databases by Robin Mathew. Update 6: NoSQL : If Only it Was that Easy . BJ Clark lays down the law on which databases are scalable: Tokyo - NO, Redis - NO, Voldemort - YES, MongoDB - Not Yet, Cassandra - Probably, Amazon S3 - YES * 2, MySQL - NO. The real thing to point out is that if you are being held back from making something super awesome because you can’t choose a database, you are doing it wrong. Update 5: Exciting stuff happening in Japan at this Key-Value Storage meeting in Tokyo . Presentations on Groonga, Senna, Lux IO, Tokyo-Cabinet, Tx, repcached, Kai, Cagra, kumofs, ROMA, and Flare. Update 4: NoSQL and the Relational Model: don’t throw the baby out with the bathwater by Matthew Willson. So my key point is, this kind of modelling is WORTH DOING, regardless of which database tool you end up using for physical storage. Update 3: Choosing a non-relational database
5 0.175111 498 high scalability-2009-01-20-Product: Amazon's SimpleDB
Introduction: Update 35 : How and Why Glue is Using Amazon SimpleDB instead of a Relational Database . Discusses a key design decision that required duplicating data in order to mimic RDBMS joins: Given the trade off between potential inconsistencies and scalability, social services have to choose the latter. Update 34 : Apparently Amazon pulled this article. I'm not sure what that means. Maybe time went backwards or something? Amazon dramatically drops SimpleDB pricing to $0.25 per GB per month from $1.50 per GB . This puts SimpleDB on par with Google App Engine . They also announced a few new features: a SQL-like SELECT API as well as a Batch Put operation to streamline uploading of multiple items or attributes . One of the complaints against SimpleDB is that programmers end up writing too much code to do simple things. These features and a much cheaper price should help considerably. And you can store lots of data now. GAE is still capped. Update 33 : Amazon announces
6 0.15378201 468 high scalability-2008-12-17-Ringo - Distributed key-value storage for immutable data
7 0.15244593 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
8 0.15082899 306 high scalability-2008-04-21-The Search for the Source of Data - How SimpleDB Differs from a RDBMS
9 0.1494486 589 high scalability-2009-05-05-Drop ACID and Think About Data
10 0.14830254 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
11 0.13315664 849 high scalability-2010-06-28-VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
12 0.13169864 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
13 0.12793207 1470 high scalability-2013-06-05-A Simple 6 Step Transition Guide for Moving Away from X to AWS
14 0.12710156 1180 high scalability-2012-01-24-The State of NoSQL in 2012
15 0.12584716 184 high scalability-2007-12-13-Amazon SimpleDB - Scalable Cloud Database
16 0.12023581 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability
17 0.11943223 1309 high scalability-2012-08-22-Cloud Deployment: It’s All About Cloud Automation
18 0.11817552 935 high scalability-2010-11-05-Hot Scalability Links For November 5th, 2010
topicId topicWeight
[(0, 0.204), (1, 0.099), (2, -0.031), (3, 0.054), (4, 0.03), (5, 0.096), (6, -0.075), (7, -0.148), (8, 0.06), (9, -0.085), (10, 0.009), (11, -0.022), (12, -0.024), (13, 0.013), (14, 0.022), (15, -0.03), (16, -0.003), (17, 0.042), (18, -0.03), (19, -0.037), (20, -0.045), (21, -0.015), (22, 0.055), (23, 0.03), (24, 0.012), (25, -0.022), (26, 0.057), (27, 0.028), (28, 0.076), (29, -0.065), (30, -0.046), (31, 0.032), (32, 0.014), (33, -0.073), (34, -0.009), (35, -0.021), (36, 0.026), (37, 0.027), (38, -0.032), (39, -0.036), (40, 0.026), (41, -0.038), (42, 0.051), (43, 0.028), (44, 0.025), (45, 0.038), (46, -0.037), (47, -0.004), (48, 0.023), (49, 0.027)]
simIndex simValue blogId blogTitle
same-blog 1 0.96483666 736 high scalability-2009-11-04-Damn, Which Database do I Use Now?
Introduction: With so many database options available these days, like for the rest of life, it's natural to wonder how it all fits together . Amazon complicated, or rather expanded the available options by introducing RDS, their relational database service . RDS is MySQL safely cocooned as a manageable cloud element, resting boldly within an energy providing elastic CPU pool , supported by a virtually infinite supply of very capable virtualized storage . MySQL in AWS is now easy to start, stop, monitor, backup, snapshot, expand, and effortlessly move up and down the instance hierarchy. What it's not, contrary to what you might expect, is a scale-out solution, it's a scale-up solution. You get more by buying a bigger instance, not by horizontally adding more instances. There's a limit . Admittedly a larger limit now with Amazon's new high memory instances . That's OK, well maybe not for people who helped grow Amazon's ecosystem by offering a similar product, but so many projects use M
2 0.77937508 498 high scalability-2009-01-20-Product: Amazon's SimpleDB
Introduction: Update 35 : How and Why Glue is Using Amazon SimpleDB instead of a Relational Database . Discusses a key design decision that required duplicating data in order to mimic RDBMS joins: Given the trade off between potential inconsistencies and scalability, social services have to choose the latter. Update 34 : Apparently Amazon pulled this article. I'm not sure what that means. Maybe time went backwards or something? Amazon dramatically drops SimpleDB pricing to $0.25 per GB per month from $1.50 per GB . This puts SimpleDB on par with Google App Engine . They also announced a few new features: a SQL-like SELECT API as well as a Batch Put operation to streamline uploading of multiple items or attributes . One of the complaints against SimpleDB is that programmers end up writing too much code to do simple things. These features and a much cheaper price should help considerably. And you can store lots of data now. GAE is still capped. Update 33 : Amazon announces
3 0.77101994 655 high scalability-2009-07-12-SPHiveDB: A mixture of the Key-Value Store and the Relational Database.
Introduction: The Key/Value Store becames more and more popular. When we use the Key/Value Store to store objects, we need to serialize/deserialize the objects as binary buffer. We have many ways to serialize/deserialize objects. A possible way is to use the Relational Database. Every value we store in the Key/Value Store is a SQLite instance. We can use the power of the Relational Database to manipulate the value. The SQL is very powerful for processing query request. SPHiveDB = TokyoCabinet + SQLite http://code.google.com/p/sphivedb/ SPHiveDB is a server for sqlite database. It use JSON-RPC over HTTP to expose a network interface to use SQLite database. It supports combining multiple SQLite databases into one file ( through tokyo cabinet ). It also supports the use of multiple files.
4 0.76843232 737 high scalability-2009-11-05-A Yes for a NoSQL Taxonomy
Introduction: NorthScale's Steven Yen in his highly entertaining NoSQL is a Horseless Carriage presentation has come up with a NoSQL taxonomy that thankfully focuses a little more on what NoSQL is, than what it isn't : key‐value‐cache memcached, repcached, coherence, infinispan, eXtreme scale, jboss cache, velocity, terracoqa key‐value‐store keyspace, flare, schema‐free, RAMCloud eventually‐consistent key‐value‐store dynamo, voldemort, Dynomite, SubRecord, Mo8onDb, Dovetaildb ordered‐key‐value‐store tokyo tyrant, lightcloud, NMDB, luxio, memcachedb, actord data‐structures server redis tuple‐store gigaspaces, coord, apache river object database ZopeDB, db4o, Shoal document store CouchDB, Mongo, Jackrabbit, XML Databases, ThruDB, CloudKit, Perservere, Riak Basho, Scalaris wide columnar store BigTable, Hbase, Cassandra, Hypertable, KAI, OpenNeptune, Qbase, KDI "Who will win?"
5 0.76194501 187 high scalability-2007-12-14-The Current Pros and Cons List for SimpleDB
Introduction: Not surprisingly opinions on SimpleDB vary from it sucks, don't take my database, to it will change the world, who needs a database anyway? From a quick survey of the blogosphere , here's where SimpleDB stands at the moment: SimpleDB Cons No SLA. We don't know how reliable it will be, how fast it will be, or how consistent the performance will be. Consistency constraints are relaxed. Reading data immediately after a write may not reflect the latest updates. To programmers used to transactions, this may be surprising, but many people think this is one of the tradeoffs that needs to be made to scale. Database is a core competency. If you don't control your database you can't out compete your competition. When your database is out of your control you can't guarantee it will work properly. You can't create the proper indexes and other optimizations. No join or IN operator. You'll need to do multiple client side calls to simulate joins, which will be slow. No
6 0.74346316 925 high scalability-2010-10-22-Paper: Netflix’s Transition to High-Availability Storage Systems
7 0.73736835 670 high scalability-2009-08-05-Anti-RDBMS: A list of distributed key-value stores
8 0.72863358 306 high scalability-2008-04-21-The Search for the Source of Data - How SimpleDB Differs from a RDBMS
9 0.72237158 732 high scalability-2009-10-29-Digg - Looking to the Future with Cassandra
10 0.7196483 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
11 0.71294886 779 high scalability-2010-02-16-Seven Signs You May Need a NoSQL Database
12 0.71153015 1092 high scalability-2011-08-04-Jim Starkey is Creating a Brave New World by Rethinking Databases for the Cloud
13 0.71146584 770 high scalability-2010-02-03-NoSQL Means Never Having to Store Blobs Again
14 0.69306427 1348 high scalability-2012-10-26-Stuff The Internet Says On Scalability For October 26, 2012
15 0.69090372 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
16 0.68966174 589 high scalability-2009-05-05-Drop ACID and Think About Data
17 0.68870485 785 high scalability-2010-02-26-MySQL and Memcached: End of an Era?
18 0.68649548 849 high scalability-2010-06-28-VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
19 0.68266511 1025 high scalability-2011-04-16-The NewSQL Market Breakdown
20 0.68242103 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
topicId topicWeight
[(1, 0.142), (2, 0.194), (10, 0.083), (47, 0.021), (51, 0.028), (56, 0.02), (61, 0.102), (79, 0.131), (86, 0.155), (94, 0.057)]
simIndex simValue blogId blogTitle
same-blog 1 0.92381126 736 high scalability-2009-11-04-Damn, Which Database do I Use Now?
Introduction: With so many database options available these days, like for the rest of life, it's natural to wonder how it all fits together . Amazon complicated, or rather expanded the available options by introducing RDS, their relational database service . RDS is MySQL safely cocooned as a manageable cloud element, resting boldly within an energy providing elastic CPU pool , supported by a virtually infinite supply of very capable virtualized storage . MySQL in AWS is now easy to start, stop, monitor, backup, snapshot, expand, and effortlessly move up and down the instance hierarchy. What it's not, contrary to what you might expect, is a scale-out solution, it's a scale-up solution. You get more by buying a bigger instance, not by horizontally adding more instances. There's a limit . Admittedly a larger limit now with Amazon's new high memory instances . That's OK, well maybe not for people who helped grow Amazon's ecosystem by offering a similar product, but so many projects use M
2 0.90395033 1626 high scalability-2014-04-04-Stuff The Internet Says On Scalability For April 4th, 2014
Introduction: Hey, it's HighScalability time: The world ends not with a bang, but with 1 exaFLOP of bitcoin whimpers. Quotable Quotes: @EtienneRoy : Algorithm: you must encode and leverage your ignorance, not only your knowledge #hadoopsummit - enthralling Chris Brenny : A material is nothing without a process. While the constituent formulation imbues the final product with fundamental properties, the bridge between material and function has a dramatic effect on its perception and use. @gallifreya n: Using AWS c1, m1, m2? @adrianco says don't. c3, m3, r3 are now better and cheaper. #cloudconnect #ccevent @christianhern : Mobile banking in the UK: 1,800 transactions per MINUTE. A "seismic shift" that banks were unprepared for While we are waiting for that epic article deeply comparing Google's Cloud with AWS, we have Adrian Cockcroft's highly hopped slide comparing the two . Google: no enterprise customers, no reservation options, need m
3 0.89785248 371 high scalability-2008-08-24-A Scalable, Commodity Data Center Network Architecture
Introduction: Looks interesting... Abstract: Today’s data centers may contain tens of thousands of computers with significant aggregate bandwidth requirements. The network architecture typically consists of a tree of routing and switching elements with progressively more specialized and expensive equipment moving up the network hierarchy. Unfortunately, even when deploying the highest-end IP switches/routers, resulting topologies may only support 50% of the aggregate bandwidth available at the edge of the network, while still incurring tremendous cost. Nonuniform bandwidth among data center nodes complicates application design and limits overall system performance. In this paper, we show how to leverage largely commodity Ethernet switches to support the full aggregate bandwidth of clusters consisting of tens of thousands of elements. Similar to how clusters of commodity computers have largely replaced more specialized SMPs and MPPs, we argue that appropriately architected and interconnected commodi
4 0.88774395 454 high scalability-2008-12-01-Deploying MySQL Database in Solaris Cluster Environments
Introduction: MySQL™ database, an open source database, delivers high performance and reliability while keeping costs low by eliminating licensing fees. The Solaris™ Cluster product is an integrated hardware and software environment that can be used to create highly-available data services. This article explains how to deploy the MySQL database in a Solaris Cluster environment. The article addresses the following topics: * "Advantages of Deploying MySQL Database with Solaris Cluster" on page 1 discusses the benefits provided by a Solaris Cluster deployment of the MySQL database. * "Overview of Solaris Cluster" on page 2 provides a high-level description of the hardware and software components of the Solaris Cluster. * "Installation and Configuration" on page 8 explains the procedure for deploying the MySQL database on a Solaris Cluster. This article assumes that readers have a basic understanding of Solaris Cluster and MySQL database installation and administration.
Introduction: We've long known one of the virtues of the cloud is, through the magic of services and automation, that systems can be shut or tuned down when not in use. What may be surprising is how much money can be saved. This aspect of cloudiness got a lot of pub at AWS re:Invent and is being rebranded under the term Cost-Aware Architecture . An interesting example was given by Ryan Park, Pinterest’s technical operations lead: 20% of their systems are shutdown after hours in response to traffic loads Reserved instances are used for standard traffic On-demand and spot instances are used to handle the elastic load throughout the day. When more servers are needed for an auto-scaled service, spot requests are opened and on-demand instances are started at the same time. Most services are targeted to run at about 50% on-demand and 50% spot. Watchdog processes continually check what's running. More instances are launched when needed and terminated when not needed. If spot prices spik
6 0.88278711 978 high scalability-2011-01-26-Google Pro Tip: Use Back-of-the-envelope-calculations to Choose the Best Design
7 0.88056964 1180 high scalability-2012-01-24-The State of NoSQL in 2012
8 0.87832844 514 high scalability-2009-02-18-Numbers Everyone Should Know
9 0.87606865 1018 high scalability-2011-04-07-Paper: A Co-Relational Model of Data for Large Shared Data Banks
10 0.87250096 853 high scalability-2010-07-08-Cloud AWS Infrastructure vs. Physical Infrastructure
11 0.87176442 1344 high scalability-2012-10-19-Stuff The Internet Says On Scalability For October 19, 2012
12 0.87172425 1649 high scalability-2014-05-16-Stuff The Internet Says On Scalability For May 16th, 2014
13 0.87143546 1186 high scalability-2012-02-02-The Data-Scope Project - 6PB storage, 500GBytes-sec sequential IO, 20M IOPS, 130TFlops
14 0.8710193 1041 high scalability-2011-05-15-Building a Database remote availability site
15 0.87069809 498 high scalability-2009-01-20-Product: Amazon's SimpleDB
16 0.86965805 301 high scalability-2008-04-08-Google AppEngine - A First Look
17 0.86918235 776 high scalability-2010-02-12-Hot Scalability Links for February 12, 2010
18 0.86776364 1448 high scalability-2013-04-29-AWS v GCE Face-off and Why Innovation Needs Lower Cost Infrastructures
19 0.86759079 129 high scalability-2007-10-23-Hire Facebook, Ning, and Salesforce to Scale for You
20 0.86734706 716 high scalability-2009-10-06-Building a Unique Data Warehouse