high_scalability high_scalability-2010 high_scalability-2010-779 knowledge-graph by maker-knowledge-mining
Source: html
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
sentIndex sentText sentNum sentScore
1 While exploring deep into some dusty old library stacks, I dug up Nostradamus' long lost NoSQL codex. [sent-1, score-0.353]
2 Strangely, it also gave the plot to the next Dan Brown novel, but I left that out for reasons of sanity. [sent-3, score-0.097]
3 About NoSQL, here is what Nosty (his friends call him Nosty) predicted are the signs you may need a NoSQL database. [sent-4, score-0.202]
4 You noticed a lot of your database fields are really serialized complex objects in disguise . [sent-7, score-0.445]
5 Storing serialized objects in a relational database is like being on the pill while trying to get pregnant, a bit counter productive. [sent-9, score-0.653]
6 Using a standard query language has become too confining . [sent-11, score-0.095]
7 Each has their own completely different query mechanism . [sent-16, score-0.089]
8 Hammers while wonderfully versatile, can not make a nice latte. [sent-18, score-0.093]
9 You really feel like protesting something, but all the really cool causes are full up . [sent-21, score-0.277]
10 Protesting the many centuries of relational database hegemony is a first rate cause you can be proud of. [sent-22, score-0.316]
11 Think of all the stirring chants: "Let My Schema Go! [sent-23, score-0.13]
12 " You stepped in a giant pile of impedance mismatch and need to wash off your shoes . [sent-26, score-0.592]
13 Maybe whatever product you are trying to build would be better represented by a graph? [sent-27, score-0.164]
14 Maintaining a completely separate object caching system on top of an already beefy table storage system, has started to seem a little silly . [sent-31, score-0.315]
15 It's a massive duplication of effort, resources, and the consistency problems are brutal. [sent-32, score-0.107]
16 The Four Horseman contract you to build a fast and infinitely scalable website to help crowd source their new startup: EndOfTheWorld. [sent-33, score-0.309]
17 Only time will tell if Nostradamus is as accurate with his NoSQL predictions as he has been with everything else. [sent-35, score-0.182]
wordName wordTfidf (topN-words)
[('nostradamus', 0.306), ('nosty', 0.306), ('protesting', 0.277), ('serialized', 0.186), ('nosql', 0.151), ('dusty', 0.139), ('hammers', 0.139), ('dug', 0.139), ('wash', 0.139), ('beefy', 0.13), ('centuries', 0.13), ('impedance', 0.13), ('stirring', 0.13), ('crowd', 0.124), ('pill', 0.12), ('brown', 0.116), ('mismatch', 0.113), ('stepped', 0.113), ('versatile', 0.113), ('toolbox', 0.11), ('duplication', 0.107), ('strangely', 0.103), ('predictions', 0.103), ('signs', 0.102), ('chances', 0.1), ('predicted', 0.1), ('objects', 0.098), ('schemaless', 0.098), ('pile', 0.097), ('plot', 0.097), ('proud', 0.097), ('table', 0.096), ('standard', 0.095), ('infinitely', 0.094), ('wonderfully', 0.093), ('contract', 0.091), ('relational', 0.089), ('completely', 0.089), ('bother', 0.088), ('viewing', 0.088), ('convenient', 0.088), ('trying', 0.086), ('stacks', 0.084), ('noticed', 0.084), ('accurate', 0.079), ('represented', 0.078), ('fields', 0.077), ('dan', 0.075), ('exploring', 0.075), ('counter', 0.074)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999988 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
2 0.17815524 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
3 0.15343481 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
4 0.13922292 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
Introduction: We've asked What The Heck Are You Actually Using NoSQL For? . We've asked 101 Questions To Ask When Considering A NoSQL Database . We've even had a webinar What Should I Do? Choosing SQL, NoSQL or Both for Scalable Web Applications . Now we get to the point of considering use cases and which systems might be appropriate for those use cases. What are your options? First, let's cover what are the various data models. These have been adapted from Emil Eifrem and NoSQL databases . Document Databases Lineage: Inspired by Lotus Notes. Data model: Collections of documents, which contain key-value collections. Example: CouchDB, MongoDB Good at: Natural data modeling. Programmer friendly. Rapid development. Web friendly, CRUD. Graph Databases Lineage: Euler and graph theory. Data model: Nodes & relationships, both which can hold key-value pairs Example: AllegroGraph, InfoGrid, Neo4j Good at: Rock complicated graph problems. Fast.
5 0.11813029 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
Introduction: This is a guest post by Frédéric Faure (architect at Ysance ), you can follow him on twitter . Data storage has always been one of the most difficult problems to address, especially as the quantity of stored data is constantly increasing. This is not simply due to the growing numbers of people regularly using the Internet, particularly with all the social networks, games and gizmos now available. Companies are also amassing more and more meticulous information relevant to their business, in order to optimize productivity and ROI (Return On Investment). I find the positioning of SQL and NoSQL (Not Only SQL) as opposites rather a shame: it’s true that the marketing wave of NoSQL has enabled the renewed promotion of a system that’s been around for quite a while, but which was only rarely considered in most cases, as after all, everything could be fitted into the « good old SQL model ». The reverse trend of wanting to make everything fit the NoSQL model is not very p
6 0.10376407 770 high scalability-2010-02-03-NoSQL Means Never Having to Store Blobs Again
7 0.092347071 739 high scalability-2009-11-09-10 NoSQL Systems Reviewed
9 0.088478498 930 high scalability-2010-10-28-NoSQL Took Away the Relational Model and Gave Nothing Back
11 0.086105876 867 high scalability-2010-07-27-YeSQL: An Overview of the Various Query Semantics in the Post Only-SQL World
12 0.085814655 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
13 0.080025472 628 high scalability-2009-06-13-Neo4j - a Graph Database that Kicks Buttox
14 0.078947559 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
15 0.078377172 327 high scalability-2008-05-27-How I Learned to Stop Worrying and Love Using a Lot of Disk Space to Scale
16 0.078151472 842 high scalability-2010-06-16-Hot Scalability Links for June 16, 2010
17 0.076058738 840 high scalability-2010-06-10-The Four Meta Secrets of Scaling at Facebook
18 0.075339273 920 high scalability-2010-10-15-Troubles with Sharding - What can we learn from the Foursquare Incident?
19 0.073675156 306 high scalability-2008-04-21-The Search for the Source of Data - How SimpleDB Differs from a RDBMS
20 0.072879657 849 high scalability-2010-06-28-VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
topicId topicWeight
[(0, 0.137), (1, 0.066), (2, -0.009), (3, 0.037), (4, 0.053), (5, 0.08), (6, -0.076), (7, -0.015), (8, 0.018), (9, -0.056), (10, -0.006), (11, 0.002), (12, -0.083), (13, 0.018), (14, 0.034), (15, -0.024), (16, 0.016), (17, 0.017), (18, -0.031), (19, -0.002), (20, -0.052), (21, -0.066), (22, 0.041), (23, -0.046), (24, 0.064), (25, -0.0), (26, 0.002), (27, 0.006), (28, -0.007), (29, -0.04), (30, -0.045), (31, 0.018), (32, 0.014), (33, 0.006), (34, 0.018), (35, 0.009), (36, -0.028), (37, 0.009), (38, -0.016), (39, -0.011), (40, -0.01), (41, 0.003), (42, 0.006), (43, -0.001), (44, -0.054), (45, -0.0), (46, -0.021), (47, -0.003), (48, 0.0), (49, 0.029)]
simIndex simValue blogId blogTitle
same-blog 1 0.97796422 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
2 0.90791637 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.86685652 930 high scalability-2010-10-28-NoSQL Took Away the Relational Model and Gave Nothing Back
Introduction: Update : Benjamin Black said he was the source of the quote and also said I was wrong about what he meant. His real point: The meaning of the statement was that NoSQL systems (really the various map-reduce systems) are lacking a standard model for describing and querying and that developing one should be a high priority task for them. At the A NoSQL Evening in Palo Alto , an audience member, sorry, I couldn't tell who, said something I found really interesting: NoSQL took away the relational model and gave nothing back. The idea being that NoSQL has focussed on ease of use, scalability, performance, etc, but it has lost the idea of how data relates to other data. True to its name, the relational model is very good at capturing a managing relationships. With NoSQL all relationships have been pushed back onto the poor programmer to implement in code rather than the database managing it. We've sacrificed usability. NoSQL is about concurrency, latency, and scalability, but it
4 0.82222754 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.81738174 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
Introduction: We've asked What The Heck Are You Actually Using NoSQL For? . We've asked 101 Questions To Ask When Considering A NoSQL Database . We've even had a webinar What Should I Do? Choosing SQL, NoSQL or Both for Scalable Web Applications . Now we get to the point of considering use cases and which systems might be appropriate for those use cases. What are your options? First, let's cover what are the various data models. These have been adapted from Emil Eifrem and NoSQL databases . Document Databases Lineage: Inspired by Lotus Notes. Data model: Collections of documents, which contain key-value collections. Example: CouchDB, MongoDB Good at: Natural data modeling. Programmer friendly. Rapid development. Web friendly, CRUD. Graph Databases Lineage: Euler and graph theory. Data model: Nodes & relationships, both which can hold key-value pairs Example: AllegroGraph, InfoGrid, Neo4j Good at: Rock complicated graph problems. Fast.
6 0.81036401 872 high scalability-2010-08-05-Pairing NoSQL and Relational Data Storage: MySQL with MongoDB
7 0.80918533 667 high scalability-2009-07-31-NSFW: Hilarious Fault-Tolerance Cartoon
8 0.80099303 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
9 0.79995167 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
10 0.79980022 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
11 0.7724039 1018 high scalability-2011-04-07-Paper: A Co-Relational Model of Data for Large Shared Data Banks
12 0.75943673 935 high scalability-2010-11-05-Hot Scalability Links For November 5th, 2010
13 0.7593652 1092 high scalability-2011-08-04-Jim Starkey is Creating a Brave New World by Rethinking Databases for the Cloud
14 0.75922537 648 high scalability-2009-07-02-It Must be Crap on Relational Dabases Week
15 0.75425541 867 high scalability-2010-07-27-YeSQL: An Overview of the Various Query Semantics in the Post Only-SQL World
16 0.75184488 849 high scalability-2010-06-28-VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
17 0.74807477 770 high scalability-2010-02-03-NoSQL Means Never Having to Store Blobs Again
18 0.74098152 1025 high scalability-2011-04-16-The NewSQL Market Breakdown
19 0.72765648 1040 high scalability-2011-05-13-Stuff The Internet Says On Scalability For May 13, 2011
topicId topicWeight
[(1, 0.101), (2, 0.184), (10, 0.015), (56, 0.41), (61, 0.077), (79, 0.091), (94, 0.028)]
simIndex simValue blogId blogTitle
1 0.96290898 1394 high scalability-2013-01-25-Stuff The Internet Says On Scalability For January 25, 2013
Introduction: Sorry, Stuff the Internet Says has been called on the account of a power outage. Gods of rain and tree have interfered with thee. Instead, how about watching a little Python? (that's Monty, not the language)
same-blog 2 0.85937446 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.84078622 45 high scalability-2007-07-30-Product: SmarterStats
Introduction: SmarterStats provides a solid architecture businesses and individual end users can use to track growth and forecast internet trends. * Track your website's growth and forecast internet trends * Features over 130 report items, plus Geographic Reporting * Log comparison saving 90% of your disk space * Email Reports available in Enterprise Edition * Enhanced data mining available in both editions
4 0.82701206 732 high scalability-2009-10-29-Digg - Looking to the Future with Cassandra
Introduction: Digg has been researching ways to scale our database infrastructure for some time now. We’ve adopted a traditional vertically partitioned master-slave configuration with MySQL, and also investigated sharding MySQL with IDDB . Ultimately, these solutions left us wanting. In the case of the traditional architecture, the lack of redundancy on the write masters is painful, and both approaches have significant management overhead to keep running. Since it was already necessary to abandon data normalization and consistency to make these approaches work, we felt comfortable looking at more exotic, non-relational data stores. After considering HBase, Hypertable, Cassandra, Tokyo Cabinet/Tyrant, Voldemort, and Dynomite, we settled on Cassandra . Each system has its own strengths and weaknesses, but Cassandra has a good blend of everything. It offers column-oriented data storage, so you have a bit more structure than plain key/value stores. It operates in a distributed, highly available,
5 0.82173008 941 high scalability-2010-11-15-How Google's Instant Previews Reduces HTTP Requests
Introduction: In a strange case of synchronicity, Google just published Instant Previews: Under the hood , a very well written blog post by Matías Pelenur of the Instant Previews team, giving some fascinating inside details on how Google implemented Instant Previews . It's syncronicty because I had just posted Strategy: Biggest Performance Impact Is To Reduce The Number Of HTTP Requests and one of the major ideas behind the design Instant Previews is to reduce the number of HTTP requests through a few well chosen tricks. Cosmic! Some of what Google does to reduce HTTP requests: Data URIs , which are are base64 encodings of image data, are used instead of static images that are served from the server. This means the whole preview can be pieced together from image slices in one request as both the data and the image are returned in the same request. Google found that even though base64 encoding adds about 33% to the size of the image, tests showed that gzip-compressed data URIs are compara
6 0.81980193 1022 high scalability-2011-04-13-Paper: NoSQL Databases - NoSQL Introduction and Overview
7 0.76899493 446 high scalability-2008-11-18-Scalability Perspectives #2: Van Jacobson – Content-Centric Networking
8 0.75991273 67 high scalability-2007-08-17-What is the best hosting option?
9 0.75470507 854 high scalability-2010-07-09-Hot Scalability Links for July 9, 2010
10 0.73763382 759 high scalability-2010-01-11-Strategy: Don't Use Polling for Real-time Feeds
11 0.70713931 659 high scalability-2009-07-20-A Scalability Lament
12 0.68720645 1322 high scalability-2012-09-14-Stuff The Internet Says On Scalability For September 14, 2012
13 0.68128735 815 high scalability-2010-04-27-Paper: Dapper, Google's Large-Scale Distributed Systems Tracing Infrastructure
14 0.66070062 479 high scalability-2008-12-29-Platform virtualization - top 25 providers (software, hardware, combined)
15 0.6057151 1565 high scalability-2013-12-16-22 Recommendations for Building Effective High Traffic Web Software
16 0.60565537 245 high scalability-2008-02-12-Product: rPath - Creating and Managing Virtual Appliances
17 0.55746418 981 high scalability-2011-02-01-Google Strategy: Tree Distribution of Requests and Responses
18 0.55300385 1236 high scalability-2012-04-30-Masstree - Much Faster than MongoDB, VoltDB, Redis, and Competitive with Memcached
19 0.55297941 744 high scalability-2009-11-24-Hot Scalability Links for Nov 24 2009
20 0.55164462 1037 high scalability-2011-05-10-Viddler Architecture - 7 Million Embeds a Day and 1500 Req-Sec Peak