high_scalability high_scalability-2009 high_scalability-2009-667 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Another fun one... Should I be Worried About Scaling? What happens when the comfortable SQL world of yesterday changes out from under you? You feel like this (it uses some language picante so be advised): Here's a link to the source: http://browsertoolkit.com/fault-tolerance.png A great way to communicate the dislocation one feels when technology changes. It also gets you to wonder if those changes at the user level are completely necessary for carrying out the task? Lest you think this just an old guard reactionary sentiment, Boxed Ice chose MongoDB over CouchDB partly because "CouchDB requires map/reduce style queries which is much more complicated to work with." Related Articles It Must be Crap on Relational Dabases Week No to SQL? Anti-database movement gains steam Anti-RDBMS: A list of distributed key-value stores
sentIndex sentText sentNum sentScore
1 What happens when the comfortable SQL world of yesterday changes out from under you? [sent-5, score-0.688]
2 You feel like this (it uses some language picante so be advised): Here's a link to the source: http://browsertoolkit. [sent-6, score-0.395]
3 png A great way to communicate the dislocation one feels when technology changes. [sent-8, score-0.443]
4 It also gets you to wonder if those changes at the user level are completely necessary for carrying out the task? [sent-9, score-0.931]
5 Lest you think this just an old guard reactionary sentiment, Boxed Ice chose MongoDB over CouchDB partly because "CouchDB requires map/reduce style queries which is much more complicated to work with. [sent-10, score-0.79]
wordName wordTfidf (topN-words)
[('lest', 0.275), ('advised', 0.253), ('guard', 0.245), ('boxed', 0.245), ('ice', 0.232), ('sentiment', 0.232), ('carrying', 0.208), ('worried', 0.202), ('yesterday', 0.199), ('crap', 0.183), ('feels', 0.173), ('gains', 0.173), ('comfortable', 0.172), ('sql', 0.168), ('movement', 0.164), ('changes', 0.155), ('communicate', 0.149), ('wonder', 0.147), ('couchdb', 0.145), ('link', 0.123), ('style', 0.121), ('task', 0.119), ('complicated', 0.116), ('necessary', 0.114), ('feel', 0.111), ('stores', 0.108), ('happens', 0.105), ('fun', 0.104), ('relational', 0.095), ('completely', 0.094), ('gets', 0.094), ('language', 0.093), ('old', 0.088), ('requires', 0.087), ('list', 0.086), ('related', 0.081), ('queries', 0.081), ('must', 0.069), ('technology', 0.068), ('uses', 0.068), ('http', 0.066), ('level', 0.065), ('another', 0.064), ('source', 0.06), ('world', 0.057), ('user', 0.054), ('scaling', 0.054), ('great', 0.053), ('think', 0.052), ('distributed', 0.045)]
simIndex simValue blogId blogTitle
same-blog 1 1.0 667 high scalability-2009-07-31-NSFW: Hilarious Fault-Tolerance Cartoon
Introduction: Another fun one... Should I be Worried About Scaling? What happens when the comfortable SQL world of yesterday changes out from under you? You feel like this (it uses some language picante so be advised): Here's a link to the source: http://browsertoolkit.com/fault-tolerance.png A great way to communicate the dislocation one feels when technology changes. It also gets you to wonder if those changes at the user level are completely necessary for carrying out the task? Lest you think this just an old guard reactionary sentiment, Boxed Ice chose MongoDB over CouchDB partly because "CouchDB requires map/reduce style queries which is much more complicated to work with." Related Articles It Must be Crap on Relational Dabases Week No to SQL? Anti-database movement gains steam Anti-RDBMS: A list of distributed key-value stores
2 0.12062 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
3 0.087052107 771 high scalability-2010-02-04-Hot Scalability Links for February 4, 2010
Introduction: Lots of cool stuff happening this week... Voldemort gets rebalancing. It's one thing to shard data to scale, it's a completely different level of functionality to manage those shards intelligently. Voldemort has stepped up by adding advanced rebalancing functionality: Dynamic addition of new nodes to the cluster; Deletion of nodes from cluster; Load balancing of data inside a cluster. Microsoft Finally Opens Azure for Business. Out of the blue Microsoft opens up their platform as a service service. Good to have more competition and we'll keep an eye out for experience reports. New details on LinkedIn architecture by Greg Linden. LinkedIn appears to only use caching minimally, preferring to spend their efforts and machine resources on making sure they can recompute computations quickly than on hiding poor performance behind caching layers . The end of SQL and relational databases? by David Intersimone . For new projects, I believe, we have genuine non-relational a
4 0.085327126 465 high scalability-2008-12-14-Scaling MySQL on a 256-way T5440 server using Solaris ZFS and Java 1.7
Introduction: How to scale MySQL on a 32 core system with 256 threads? Diagonal scalability in a box. An impressive benchmark that achieved more than 79,000 SQL queries per second on a single 4 RU server! Is this real? If so what is the role of good old horizontal scalability? The goals of the benchmark: Reach a high throughput of SQL queries on a 256-way Sun SPARC Enterprise T5440 Do it 21st century style i.e. with MySQL and ZFS , not 20th century style i.e with OraSybInf... and VxFS Do it with minimal tuning i.e as close as possible as out-of-the-box
5 0.079270899 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
Introduction: It's a truism that we should choose the right tool for the job . Everyone says that. And who can disagree? The problem is this is not helpful advice without being able to answer more specific questions like: What jobs are the tools good at? Will they work on jobs like mine? Is it worth the risk to try something new when all my people know something else and we have a deadline to meet? How can I make all the tools work together? In the NoSQL space this kind of real-world data is still a bit vague. When asked, vendors tend to give very general answers like NoSQL is good for BigData or key-value access. What does that mean for for the developer in the trenches faced with the task of solving a specific problem and there are a dozen confusing choices and no obvious winner? Not a lot. It's often hard to take that next step and imagine how their specific problems could be solved in a way that's worth taking the trouble and risk. Let's change that. What problems are you using NoSQL to sol
6 0.07707347 410 high scalability-2008-10-13-SQL Server 2008 Database Performance and Scalability
7 0.076324843 995 high scalability-2011-02-24-Strategy: Eliminate Unnecessary SQL
8 0.075042307 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
9 0.07497099 867 high scalability-2010-07-27-YeSQL: An Overview of the Various Query Semantics in the Post Only-SQL World
10 0.073421635 648 high scalability-2009-07-02-It Must be Crap on Relational Dabases Week
11 0.072165325 1085 high scalability-2011-07-25-Is NoSQL a Premature Optimization that's Worse than Death? Or the Lady Gaga of the Database World?
12 0.069142058 931 high scalability-2010-10-28-Notes from A NOSQL Evening in Palo Alto
13 0.068139672 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
14 0.067678526 654 high scalability-2009-07-09-No to SQL? Anti-database movement gains steam – My Take
15 0.06655921 1032 high scalability-2011-05-02-Stack Overflow Makes Slow Pages 100x Faster by Simple SQL Tuning
16 0.066503949 139 high scalability-2007-10-30-Paper: Dynamo: Amazon’s Highly Available Key-value Store
17 0.066066541 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
18 0.06602364 739 high scalability-2009-11-09-10 NoSQL Systems Reviewed
19 0.065370165 849 high scalability-2010-06-28-VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
20 0.06481795 1440 high scalability-2013-04-15-Scaling Pinterest - From 0 to 10s of Billions of Page Views a Month in Two Years
topicId topicWeight
[(0, 0.099), (1, 0.042), (2, 0.012), (3, 0.02), (4, 0.051), (5, 0.042), (6, -0.042), (7, -0.007), (8, 0.005), (9, -0.023), (10, -0.009), (11, 0.013), (12, -0.032), (13, 0.004), (14, 0.026), (15, -0.03), (16, 0.001), (17, 0.003), (18, -0.044), (19, -0.024), (20, -0.036), (21, -0.042), (22, 0.012), (23, -0.043), (24, 0.043), (25, 0.006), (26, 0.0), (27, 0.015), (28, 0.002), (29, -0.007), (30, -0.032), (31, 0.025), (32, -0.042), (33, 0.007), (34, 0.047), (35, -0.026), (36, 0.029), (37, 0.02), (38, -0.019), (39, 0.012), (40, 0.001), (41, -0.014), (42, 0.0), (43, -0.046), (44, -0.013), (45, 0.013), (46, -0.021), (47, -0.009), (48, 0.021), (49, 0.016)]
simIndex simValue blogId blogTitle
same-blog 1 0.96967238 667 high scalability-2009-07-31-NSFW: Hilarious Fault-Tolerance Cartoon
Introduction: Another fun one... Should I be Worried About Scaling? What happens when the comfortable SQL world of yesterday changes out from under you? You feel like this (it uses some language picante so be advised): Here's a link to the source: http://browsertoolkit.com/fault-tolerance.png A great way to communicate the dislocation one feels when technology changes. It also gets you to wonder if those changes at the user level are completely necessary for carrying out the task? Lest you think this just an old guard reactionary sentiment, Boxed Ice chose MongoDB over CouchDB partly because "CouchDB requires map/reduce style queries which is much more complicated to work with." Related Articles It Must be Crap on Relational Dabases Week No to SQL? Anti-database movement gains steam Anti-RDBMS: A list of distributed key-value stores
2 0.80609828 779 high scalability-2010-02-16-Seven Signs You May Need a NoSQL Database
Introduction: While exploring deep into some dusty old library stacks, I dug up Nostradamus' long lost NoSQL codex. What are the chances? Strangely, it also gave the plot to the next Dan Brown novel, but I left that out for reasons of sanity. About NoSQL, here is what Nosty (his friends call him Nosty) predicted are the signs you may need a NoSQL database... You noticed a lot of your database fields are really serialized complex objects in disguise . Why bother with a RDBMS at all then? Storing serialized objects in a relational database is like being on the pill while trying to get pregnant, a bit counter productive. Just use a schemaless database from the start. Using a standard query language has become too confining . You just want to be free. SQL is so easy, so convenient, and so standard, it's really not a challenge anymore. You need to be different. Then NoSQL is for you. Each has their own completely different query mechanism . Your toolbox only contains a hammer . Hammers wh
3 0.7502858 867 high scalability-2010-07-27-YeSQL: An Overview of the Various Query Semantics in the Post Only-SQL World
Introduction: The NoSQL movement faults the SQL query language as the source of many of the scalability issues that we face today with traditional database approach. I think that the main reason so many people have come to see SQL as the source of all evil is the fact that, traditionally, the query language was burned into the database implementation. So by saying NoSQL you basically say "No" to the traditional non-scalable RDBMS implementations. This view has brought on a flood of alternative query languages, each aiming to solve a different aspect that is missing in the traditional SQL query approach, such as a document model, or that provides a simpler approach, such as Key/Value query. Most of the people I speak with seem fairly confused on this subject, and tend to use query semantics and architecture interchangeably. In Part I of this post i tried to provide quick overview of what each query term stands for in the context of the NoSQL world . Part II illustrates those ide
4 0.74676031 931 high scalability-2010-10-28-Notes from A NOSQL Evening in Palo Alto
Introduction: I along with 180 other people and veritable who's who of NoSQL vendors, attended the A NoSQL Evening in Palo Alto NoSQL Meetup on Tuesday. The format was a panel of 10 vendors--10gen, Basho, CouchOne, Cloudant, Cloudera, GoGrid, InfiniteGraph, Membase, Riptano, Scality--sitting in two rows of chairs in front of what seemed like a pretty diverse audience. Tim Anglade (founder, A NOSQL Summer) moderated. Tim kept things moving by asking a few leading questions and the panel chimed in with answers. Quite a few questions came from the audience, which was refreshing. Overall a genial evening with some good discussion. I was pleased that the panel members didn't just automatically slip into marketing speak. Most of the discussions were on point rather than just another excuse to hit the talking points. There were some complaints about the talk not being technical enough, but I don't think that was really the purpose of this kind of talk. The panel format is excellent at giving a wide ra
5 0.73875248 1018 high scalability-2011-04-07-Paper: A Co-Relational Model of Data for Large Shared Data Banks
Introduction: Let's play a quick game of truth or sacrilage: are SQL and NoSQL are really just two sides of the same coin? That's what Erik Meijer and Gavin Bierman would have us believe in their "we can all get along and make a lot of money" article in the Communications of the ACM, A Co-Relational Model of Data for Large Shared Data Banks . You don't believe it? It's math, so it must be true :-) Some key points: In this article we present a mathematical data model for the most common noSQL databases—namely, key/value relationships—and demonstrate that this data model is the mathematical dual of SQL's relational data model of foreign-/primary-key relationships ...we believe that our categorical data-model formalization and monadic query language will allow the same economic growth to occur for coSQL key-value stores. ...In contrast to common belief, the question of big versus small data is orthogonal to the question of SQL versus coSQL. While the coSQL model naturally supports extreme sh
6 0.72821051 930 high scalability-2010-10-28-NoSQL Took Away the Relational Model and Gave Nothing Back
8 0.70166045 737 high scalability-2009-11-05-A Yes for a NoSQL Taxonomy
9 0.68897539 935 high scalability-2010-11-05-Hot Scalability Links For November 5th, 2010
10 0.68143564 306 high scalability-2008-04-21-The Search for the Source of Data - How SimpleDB Differs from a RDBMS
11 0.67031902 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
12 0.66827482 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
13 0.656901 770 high scalability-2010-02-03-NoSQL Means Never Having to Store Blobs Again
14 0.6567117 1092 high scalability-2011-08-04-Jim Starkey is Creating a Brave New World by Rethinking Databases for the Cloud
15 0.65543151 648 high scalability-2009-07-02-It Must be Crap on Relational Dabases Week
16 0.65230185 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
18 0.64870757 670 high scalability-2009-08-05-Anti-RDBMS: A list of distributed key-value stores
19 0.64520174 1032 high scalability-2011-05-02-Stack Overflow Makes Slow Pages 100x Faster by Simple SQL Tuning
20 0.64222288 655 high scalability-2009-07-12-SPHiveDB: A mixture of the Key-Value Store and the Relational Database.
topicId topicWeight
[(2, 0.197), (47, 0.087), (61, 0.108), (70, 0.314), (79, 0.167)]
simIndex simValue blogId blogTitle
same-blog 1 0.80148661 667 high scalability-2009-07-31-NSFW: Hilarious Fault-Tolerance Cartoon
Introduction: Another fun one... Should I be Worried About Scaling? What happens when the comfortable SQL world of yesterday changes out from under you? You feel like this (it uses some language picante so be advised): Here's a link to the source: http://browsertoolkit.com/fault-tolerance.png A great way to communicate the dislocation one feels when technology changes. It also gets you to wonder if those changes at the user level are completely necessary for carrying out the task? Lest you think this just an old guard reactionary sentiment, Boxed Ice chose MongoDB over CouchDB partly because "CouchDB requires map/reduce style queries which is much more complicated to work with." Related Articles It Must be Crap on Relational Dabases Week No to SQL? Anti-database movement gains steam Anti-RDBMS: A list of distributed key-value stores
2 0.78347659 1127 high scalability-2011-09-28-Pursue robust indefinite scalability with the Movable Feast Machine
Introduction: And now for something completely different, brought to you by David Ackley and Daniel Cannon in their playfully thought provoking paper: Pursue robust indefinite scalability , wherein they try to take a fresh look at neural networks, starting from scratch. What is this strange thing called indefinite scalability ? They sound like words that don't really go together: Indefinite scalability is the property that the design can support open-ended computational growth without substantial re-engineering, in as strict as sense as can be managed. By comparison, many computer, algorithm, and network designs -- even those that address scalability -- are only finitely scalable because their scalability occurs within some finite space. For example, an in-core sorting algorithm for a 32 bit machine can only scale to billions of numbers before address space is exhausted and then that algorithm must be re-engineered. Our idea is to expose indefinitely scalable computational power to program
3 0.71507907 146 high scalability-2007-11-08-scaling drupal - an open-source infrastructure for high-traffic drupal sites
Introduction: the authors of drupal have paid considerable attention to performance and scalability. consequently even a default install running on modest hardware can easily handle the demands a small website. if you are lucky, eventually the time comes when you need to service more users than your system can handle. at some point, you'll start looking at your hardware and network deployment. read more .
4 0.66509968 295 high scalability-2008-04-02-Product: Supervisor - Monitor and Control Your Processes
Introduction: It's a sad fact of life, but processes die. I know, it's horrible. You start them, send them out into process space, and hope for the best. Yet sometimes, despite your best coding, they core dump, seg fault, or some other calamity befalls them. Unlike our messy biological world so cruelly ruled by entropy, in the digital world processes can be given another chance. They can be restarted. A greater destiny awaits. And hopefully this time the random lottery of unforeseen killing factors will be avoided and a long productive life will be had by all. This is fun code to write because it's a lot more complicated than you might think. And restarting processes is a highly effective high availability strategy. Most faults are transient, caused by an unexpected series of events. Rather than taking drastic action, like taking a node out of production or failing over, transients can be effectively masked by simply restarting failed processes. Though complexity makes it a fun problem, it's also
5 0.65536875 1256 high scalability-2012-06-04-OpenFlow-SDN is Not a Silver Bullet for Network Scalability
Introduction: Ivan Pepelnjak (CCIE#1354 Emeritus) is Chief Technology Advisor at NIL Data Communications , author of numerous webinars and advanced networking books , and a prolific blogger . He’s focusing on data center and cloud networking, network virtualization, and scalable application design. OpenFlow is an interesting emerging networking technology appearing seemingly out of nowhere with much hype and fanfare in March 2011. More than a year later, there are two commercial products based on OpenFlow ( NEC’s Programmable Flow and Nicira’s Network Virtualization Platform ) and probably less than a dozen production-grade implementations (including Google’s G-Scale network and Indiana University’s campus network ). Is this an expected result for an emerging technology or another case of overhyped technology hitting limits imposed by reality? OpenFlow-based solutions have to overcome numerous problems every emerging technology is facing, in OpenFlow’s case ranging from compatibili
6 0.63125753 803 high scalability-2010-04-05-Intercloud: How Will We Scale Across Multiple Clouds?
8 0.61923993 1018 high scalability-2011-04-07-Paper: A Co-Relational Model of Data for Large Shared Data Banks
9 0.61803758 1445 high scalability-2013-04-24-Strategy: Using Lots of RAM Often Cheaper than Using a Hadoop Cluster
10 0.61669123 235 high scalability-2008-02-02-The case against ORM Frameworks in High Scalability Architectures
11 0.61356825 1242 high scalability-2012-05-09-Cell Architectures
12 0.6132611 1048 high scalability-2011-05-27-Stuff The Internet Says On Scalability For May 27, 2011
14 0.61188275 1337 high scalability-2012-10-10-Antirez: You Need to Think in Terms of Organizing Your Data for Fetching
15 0.61140847 867 high scalability-2010-07-27-YeSQL: An Overview of the Various Query Semantics in the Post Only-SQL World
16 0.6109671 687 high scalability-2009-08-24-How Google Serves Data from Multiple Datacenters
17 0.60948426 1326 high scalability-2012-09-20-How Vimeo Saves 50% on EC2 by Playing a Smarter Game
18 0.60881996 526 high scalability-2009-03-05-Strategy: In Cloud Computing Systematically Drive Load to the CPU
19 0.60799873 862 high scalability-2010-07-20-Strategy: Consider When a Service Starts Billing in Your Algorithm Cost
20 0.6073097 897 high scalability-2010-09-08-4 General Core Scalability Patterns