high_scalability high_scalability-2010 high_scalability-2010-885 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: The world of NoSQL and alternative database implementations (i.e. non-relational) is deeply fascinating to me. I can’t help but be swept up in the whirl of planet-scale web development scalability techniques and the evolution of how developers think about building their applications knowing that with success comes the inevitable need to scale to levels almost unimaginable just five or ten years ago. I’m going to make a prediction: Developers will be expected to understand the fundamentals of how different database systems can be applied within a singular application; their strengths and weaknesses, and when it is appropriate to leverage them. There’s a lot out there about scaling relational databases. Partitioning your data over application-managed shards is a topic that has seen its fair share of attention. But I think there’s a whole slew over NoSQL databases that have been built and designed by some very smart people that are new enough that their internals aren’t we
sentIndex sentText sentNum sentScore
1 The world of NoSQL and alternative database implementations (i. [sent-1, score-0.327]
2 I can’t help but be swept up in the whirl of planet-scale web development scalability techniques and the evolution of how developers think about building their applications knowing that with success comes the inevitable need to scale to levels almost unimaginable just five or ten years ago. [sent-4, score-1.319]
3 I’m going to make a prediction: Developers will be expected to understand the fundamentals of how different database systems can be applied within a singular application; their strengths and weaknesses, and when it is appropriate to leverage them. [sent-5, score-1.082]
4 There’s a lot out there about scaling relational databases. [sent-6, score-0.219]
5 Partitioning your data over application-managed shards is a topic that has seen its fair share of attention. [sent-7, score-0.35]
6 But I think there’s a whole slew over NoSQL databases that have been built and designed by some very smart people that are new enough that their internals aren’t well understood by most developers to the same level as the typical relational database. [sent-8, score-1.057]
7 My hope is that I’m remedying that need with this new article series and, in the process, building a functional distributed key-value database with the community. [sent-9, score-0.473]
8 I’ll be documenting each stage of the process that I go through during my exploration into designing and coding each piece of this database and, with some helpful guidance from the community, evolving and sharing it for all to use – it will of course be open sourced. [sent-10, score-1.439]
wordName wordTfidf (topN-words)
[('relational', 0.219), ('slew', 0.212), ('unimaginable', 0.202), ('singular', 0.195), ('fundamentals', 0.189), ('weaknesses', 0.189), ('storyhere', 0.184), ('strengths', 0.179), ('documenting', 0.175), ('developers', 0.167), ('guidance', 0.163), ('inevitable', 0.158), ('internals', 0.154), ('prediction', 0.144), ('understood', 0.142), ('exploration', 0.14), ('deeply', 0.138), ('fair', 0.134), ('evolving', 0.132), ('stage', 0.126), ('nosql', 0.123), ('ten', 0.122), ('implementations', 0.12), ('helpful', 0.113), ('shards', 0.112), ('database', 0.11), ('coding', 0.107), ('appropriate', 0.107), ('leverage', 0.106), ('evolution', 0.105), ('piece', 0.105), ('topic', 0.104), ('five', 0.103), ('knowing', 0.103), ('success', 0.101), ('fascinating', 0.099), ('expected', 0.099), ('functional', 0.098), ('applied', 0.097), ('alternative', 0.097), ('hope', 0.095), ('process', 0.091), ('sharing', 0.09), ('partitioning', 0.09), ('levels', 0.09), ('building', 0.089), ('designing', 0.087), ('smart', 0.084), ('series', 0.081), ('think', 0.079)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
Introduction: The world of NoSQL and alternative database implementations (i.e. non-relational) is deeply fascinating to me. I can’t help but be swept up in the whirl of planet-scale web development scalability techniques and the evolution of how developers think about building their applications knowing that with success comes the inevitable need to scale to levels almost unimaginable just five or ten years ago. I’m going to make a prediction: Developers will be expected to understand the fundamentals of how different database systems can be applied within a singular application; their strengths and weaknesses, and when it is appropriate to leverage them. There’s a lot out there about scaling relational databases. Partitioning your data over application-managed shards is a topic that has seen its fair share of attention. But I think there’s a whole slew over NoSQL databases that have been built and designed by some very smart people that are new enough that their internals aren’t we
2 0.16291785 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
3 0.13593613 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
4 0.13571316 749 high scalability-2009-12-15-The Common Principles Behind the NOSQL Alternatives
Introduction: This post draws some of the common patterns behind the various NOSQL alternatives, and how they address the database scalability challenge. Read the full story here
5 0.11901852 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
Introduction: We are on the edge of two potent technological changes: Clouds and Memory Based Architectures. This evolution will rip open a chasm where new players can enter and prosper. Google is the master of disk. You can't beat them at a game they perfected. Disk based databases like SimpleDB and BigTable are complicated beasts, typical last gasp products of any aging technology before a change. The next era is the age of Memory and Cloud which will allow for new players to succeed. The tipping point will be soon. Let's take a short trip down web architecture lane: It's 1993: Yahoo runs on FreeBSD, Apache, Perl scripts and a SQL database It's 1995: Scale-up the database. It's 1998: LAMP It's 1999: Stateless + Load Balanced + Database + SAN It's 2001: In-memory data-grid. It's 2003: Add a caching layer. It's 2004: Add scale-out and partitioning. It's 2005: Add asynchronous job scheduling and maybe a distributed file system. It's 2007: Move it all into the cloud. It's 2008: C
6 0.10765336 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
7 0.10139617 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
8 0.098334737 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
9 0.097925179 875 high scalability-2010-08-09-NoSQL on the Microsoft Platform
10 0.095456481 1110 high scalability-2011-09-06-Big Data Application Platform
11 0.090950236 187 high scalability-2007-12-14-The Current Pros and Cons List for SimpleDB
12 0.09012267 748 high scalability-2009-11-30-Why Existing Databases (RAC) are So Breakable!
13 0.08946459 739 high scalability-2009-11-09-10 NoSQL Systems Reviewed
15 0.087462008 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
18 0.085647784 785 high scalability-2010-02-26-MySQL and Memcached: End of an Era?
19 0.08558578 320 high scalability-2008-05-17-DB2 Express-C
20 0.085292339 799 high scalability-2010-03-23-Digg: 4000% Performance Increase by Sorting in PHP Rather than MySQL
topicId topicWeight
[(0, 0.155), (1, 0.041), (2, 0.016), (3, 0.053), (4, 0.076), (5, 0.072), (6, -0.097), (7, -0.072), (8, -0.017), (9, -0.019), (10, -0.017), (11, 0.038), (12, -0.061), (13, 0.037), (14, 0.034), (15, -0.054), (16, 0.038), (17, -0.007), (18, -0.03), (19, 0.014), (20, -0.043), (21, -0.019), (22, 0.025), (23, -0.022), (24, 0.056), (25, -0.022), (26, -0.034), (27, -0.055), (28, -0.046), (29, 0.003), (30, -0.017), (31, 0.018), (32, 0.029), (33, 0.011), (34, 0.023), (35, -0.039), (36, -0.051), (37, -0.044), (38, 0.02), (39, 0.016), (40, 0.01), (41, 0.003), (42, -0.007), (43, -0.017), (44, -0.03), (45, 0.015), (46, 0.017), (47, -0.035), (48, -0.017), (49, 0.024)]
simIndex simValue blogId blogTitle
same-blog 1 0.97106743 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
Introduction: The world of NoSQL and alternative database implementations (i.e. non-relational) is deeply fascinating to me. I can’t help but be swept up in the whirl of planet-scale web development scalability techniques and the evolution of how developers think about building their applications knowing that with success comes the inevitable need to scale to levels almost unimaginable just five or ten years ago. I’m going to make a prediction: Developers will be expected to understand the fundamentals of how different database systems can be applied within a singular application; their strengths and weaknesses, and when it is appropriate to leverage them. There’s a lot out there about scaling relational databases. Partitioning your data over application-managed shards is a topic that has seen its fair share of attention. But I think there’s a whole slew over NoSQL databases that have been built and designed by some very smart people that are new enough that their internals aren’t we
2 0.84256285 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
3 0.80923474 648 high scalability-2009-07-02-It Must be Crap on Relational Dabases Week
Introduction: It's hard to be a relational database lately. After years of faithful service everywhere you look the world is turning against you: Recently at the NoSQL conference 150 revolutionaries met with their new anti-RDBMS arms suppliers. And you know what happens when revolutionaries are motivated, educated, funded, and well armed. The revolution has gone mainstream when Computerworld writes No to SQL? Anti-database movement gains steam . It's not just whispers anymore, it's everywhere. And perennial revolutionary Michael Stonebraker runs from blog to blog shouting the The End of a DBMS Era (Might be Upon Us) . Relational vendors are selling legacy software, are 50x slower than other alternatives, and that can not stand. The Greek Chorus on Hacker News sings of anger and lies. Certainly some say stick with the past. It's your fault, you aren't doing it right, give us another chance and all will be as it ever was. Some smirk saying this is nothing but a return to a more ancient
4 0.80438119 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
5 0.77760845 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
6 0.77446741 930 high scalability-2010-10-28-NoSQL Took Away the Relational Model and Gave Nothing Back
7 0.77136153 1025 high scalability-2011-04-16-The NewSQL Market Breakdown
8 0.76465684 872 high scalability-2010-08-05-Pairing NoSQL and Relational Data Storage: MySQL with MongoDB
9 0.74882877 935 high scalability-2010-11-05-Hot Scalability Links For November 5th, 2010
10 0.74438959 1054 high scalability-2011-06-06-NoSQL Pain? Learn How to Read-write Scale Without a Complete Re-write
11 0.73792887 749 high scalability-2009-12-15-The Common Principles Behind the NOSQL Alternatives
12 0.73336369 785 high scalability-2010-02-26-MySQL and Memcached: End of an Era?
13 0.73236561 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
14 0.71616703 737 high scalability-2009-11-05-A Yes for a NoSQL Taxonomy
15 0.71419293 875 high scalability-2010-08-09-NoSQL on the Microsoft Platform
16 0.70542461 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
17 0.70535541 654 high scalability-2009-07-09-No to SQL? Anti-database movement gains steam – My Take
18 0.70532888 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
19 0.69134527 799 high scalability-2010-03-23-Digg: 4000% Performance Increase by Sorting in PHP Rather than MySQL
topicId topicWeight
[(1, 0.042), (2, 0.301), (40, 0.065), (61, 0.147), (79, 0.075), (92, 0.271)]
simIndex simValue blogId blogTitle
1 0.91240084 839 high scalability-2010-06-09-Paper: Propagation Networks: A Flexible and Expressive Substrate for Computation
Introduction: Alexey Radul in his fascinating 174 page dissertation Propagation Networks: A Flexible and Expressive Substrate for Computation , offers to help us break free of the tyranny of linear time by arranging computation as a network of autonomous but interconnected machines . We can do this by organizing computation as a network of interconnected machines of some kind, each of which is free to run when it pleases, propagating information around the network as proves possible. The consequence of this freedom is that the structure of the aggregate does not impose an order of time. The abstract from his thesis is : In this dissertation I propose a shift in the foundations of computation. Modern programming systems are not expressive enough. The traditional image of a single computer that has global effects on a large memory is too restrictive. The propagation paradigm replaces this with computing by networks of local, independent, stateless machines interconnected with stateful storage
2 0.87107116 352 high scalability-2008-07-18-Robert Scoble's Rules for Successfully Scaling Startups
Introduction: Robert Scoble in an often poignant FriendFeed thread commiserating PodTech's unfortunate end, shared what he learned about creating a successful startup. Here's a summary of a Robert's rules and why Machiavelli just may agree with them: Have a story. Have everyone on board with that story. If anyone goes off of that story, make sure they get on board immediately or fire them. Make sure people are judged by the revenues they bring in. Those that bring in revenues should get to run the place. People who don't bring in revenues should get fewer and fewer responsibilities, not more and more. Work ONLY for a leader who will make the tough decisions. Build a place where excellence is expected, allowed, and is enabled. Fire idiots quickly. If your engineering team can't give a media team good measurements, the entire company is in trouble. Only things that are measured ever get improved. When your stars aren't listened to the company is in trouble. Getting rid of t
3 0.86794412 1636 high scalability-2014-04-23-Here's a 1300 Year Old Solution to Resilience - Rebuild, Rebuild, Rebuild
Introduction: How is it possible that a wooden Shinto shrine built in the 7th century is still standing? The answer depends on how you answer this philosophical head scratcher: With nearly every cell in your body continually being replaced, are you still the same person? The Ise Grand Shrine has been in continuous existence for over 1300 years because every twenty years an exact replica has been rebuilt on an adjacent footprint. The former temple is then dismantled. Now that's resilience. If you want something to last make it a living part of a culture. It's not so much the building that is remade, what is rebuilt and passed down from generation to generation is the meme that the shrine is important and worth preserving. The rest is an unfolding of that imperative. You can see echoes of this same process in Open Source projects like Linux and the libraries and frameworks that get themselves reconstructed in each new environment. The patterns of recurrence in software are the result of Darw
4 0.84568185 532 high scalability-2009-03-11-Sharding and Connection Pools
Introduction: Hi we are looking at sharding our existing Java/Oracle based application. We are looking to make the app servers able to process requests for multiple (any?) shard. The concern that has come up is the amount of memory that would be consumed by having so many connection pools on one app server. Additionally there is concern about having so many physical connections to the database server coming from all the various app servers that may talk to that particular shard. I was wondering if anyone else has dealt with this issue and how you resolved it? Thanks, Scott
same-blog 5 0.84388274 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
Introduction: The world of NoSQL and alternative database implementations (i.e. non-relational) is deeply fascinating to me. I can’t help but be swept up in the whirl of planet-scale web development scalability techniques and the evolution of how developers think about building their applications knowing that with success comes the inevitable need to scale to levels almost unimaginable just five or ten years ago. I’m going to make a prediction: Developers will be expected to understand the fundamentals of how different database systems can be applied within a singular application; their strengths and weaknesses, and when it is appropriate to leverage them. There’s a lot out there about scaling relational databases. Partitioning your data over application-managed shards is a topic that has seen its fair share of attention. But I think there’s a whole slew over NoSQL databases that have been built and designed by some very smart people that are new enough that their internals aren’t we
6 0.76296872 357 high scalability-2008-07-26-Google's Paxos Made Live – An Engineering Perspective
7 0.75847507 564 high scalability-2009-04-10-counting # of views, calculating most-least viewed
8 0.7541011 595 high scalability-2009-05-08-Publish-subscribe model does not scale?
9 0.75319225 1074 high scalability-2011-07-06-11 Common Web Use Cases Solved in Redis
10 0.75200969 157 high scalability-2007-11-16-Product: lbpool - Load Balancing JDBC Pool
11 0.75175625 1017 high scalability-2011-04-06-Netflix: Run Consistency Checkers All the time to Fixup Transactions
12 0.75107729 628 high scalability-2009-06-13-Neo4j - a Graph Database that Kicks Buttox
13 0.75054598 1234 high scalability-2012-04-26-Akaros - an open source operating system for manycore architectures
14 0.74865896 717 high scalability-2009-10-07-How to Avoid the Top 5 Scale-Out Pitfalls
15 0.74745125 252 high scalability-2008-02-18-limit on the number of databases open
16 0.74661636 850 high scalability-2010-06-30-Paper: GraphLab: A New Framework For Parallel Machine Learning
17 0.74641556 943 high scalability-2010-11-16-Facebook's New Real-time Messaging System: HBase to Store 135+ Billion Messages a Month
18 0.74595183 772 high scalability-2010-02-05-High Availability Principle : Concurrency Control
19 0.74592692 928 high scalability-2010-10-26-Scaling DISQUS to 75 Million Comments and 17,000 RPS
20 0.74506414 1135 high scalability-2011-10-31-15 Ways to Make Your Application Feel More Responsive under Google App Engine