high_scalability high_scalability-2010 high_scalability-2010-785 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: If you look at the early days of this blog, when web scalability was still in its heady bloom of youth, many of the articles had to do with leveraging MySQL and memcached . Exciting times. Shard MySQL to handle high write loads, cache objects in memcached to handle high read loads, and then write a lot of glue code to make it all work together. That was state of the art, that was how it was done. The architecture of many major sites still follow this pattern today, largely because with enough elbow grease, it works. This was a pre-cloud, relational database dominated world, built from parts scrounged from the remnants of enterprises and datacenters past. Twitter and Digg started in this era, but are evolving into something different, as scaling pressures increase and new purpose built technologies pop into being. With a little perspective, it's clear the MySQL+memcached era is passing. It will stick around for a while. Old technologies seldom fade away completely. Some still
sentIndex sentText sentNum sentScore
1 If you look at the early days of this blog, when web scalability was still in its heady bloom of youth, many of the articles had to do with leveraging MySQL and memcached . [sent-1, score-0.457]
2 Shard MySQL to handle high write loads, cache objects in memcached to handle high read loads, and then write a lot of glue code to make it all work together. [sent-3, score-0.299]
3 The architecture of many major sites still follow this pattern today, largely because with enough elbow grease, it works. [sent-5, score-0.219]
4 This was a pre-cloud, relational database dominated world, built from parts scrounged from the remnants of enterprises and datacenters past. [sent-6, score-0.185]
5 Twitter and Digg started in this era, but are evolving into something different, as scaling pressures increase and new purpose built technologies pop into being. [sent-7, score-0.25]
6 With a little perspective, it's clear the MySQL+memcached era is passing. [sent-8, score-0.234]
7 And the Internet will not completely replace that archaic electro-magnetic broadcast technology called TV, but the majority will move on into a new era. [sent-13, score-0.284]
8 Digg declared their entrance into a new era in a post on their blog titled Looking to the future with Cassandra , saying: The fundamental problem is endemic to the relational database mindset, which places the burden of computation on reads rather than writes. [sent-16, score-0.799]
9 This is completely wrong for large-scale web applications, where response time is critical. [sent-17, score-0.107]
10 Twitter has also declared their move in the article Cassandra @ Twitter: An Interview with Ryan King . [sent-21, score-0.169]
11 We have a system in place based on shared mysql + memcache but its quickly becoming prohibitively costly (in terms of manpower) to operate. [sent-23, score-0.217]
12 It's clear that many of the ideas behind MySQL+memcached were on the mark, we see them preserved in the new systems, it's just that the implementation was a bit clunky. [sent-25, score-0.173]
13 Developers have moved in, filled the gaps, sanded the corners, and made a new sturdy platform which will itself form the basis for a new ecosystem and a new era. [sent-26, score-0.417]
14 It's always a bit sad to see an era pass, but it's not all that often we get to notice as it's happening. [sent-27, score-0.32]
15 We can enjoy what has gone before, but we can also get pumped to jump in with both feet and create the future. [sent-28, score-0.188]
16 I think that MySQL+memcached is still the default choice and I don't think it is going away in the high-scale market . [sent-31, score-0.123]
17 The death of Memcached is greatly exaggerated The death of Memcached is greatly exaggerated by Mark Atwood . [sent-32, score-0.502]
18 MySQL+Memcached is still the workhorse by Mark Atwood. [sent-39, score-0.234]
19 You want a workhorse that you know how to use, you know you can get gear for at the blacksmith and the tackle shop, and that you know you can hire field hands who know how to use it well and take of properly. [sent-41, score-0.497]
20 I expect we’ll see more large scale websites decide that instead of treating a SQL database as a denormalized key-value pair store that they would rather use a NoSQL database . [sent-44, score-0.16]
wordName wordTfidf (topN-words)
[('era', 0.234), ('curt', 0.23), ('memcached', 0.223), ('mark', 0.178), ('declared', 0.169), ('death', 0.128), ('greatly', 0.123), ('still', 0.123), ('mysql', 0.121), ('stick', 0.121), ('endemic', 0.111), ('heady', 0.111), ('liebydennis', 0.111), ('othersby', 0.111), ('workhorse', 0.111), ('youth', 0.111), ('relational', 0.108), ('completely', 0.107), ('manpower', 0.104), ('pumped', 0.104), ('grease', 0.1), ('archaic', 0.1), ('entrance', 0.1), ('fade', 0.1), ('prohibitively', 0.096), ('elbow', 0.096), ('pressures', 0.096), ('sturdy', 0.096), ('preserved', 0.096), ('loads', 0.095), ('nosql', 0.091), ('corners', 0.09), ('gear', 0.09), ('moved', 0.09), ('seldom', 0.088), ('sad', 0.086), ('feet', 0.084), ('dare', 0.084), ('gaps', 0.084), ('mindset', 0.083), ('denormalized', 0.08), ('treating', 0.08), ('ride', 0.079), ('pop', 0.077), ('dominated', 0.077), ('new', 0.077), ('glue', 0.076), ('know', 0.074), ('completion', 0.074), ('shop', 0.074)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000002 785 high scalability-2010-02-26-MySQL and Memcached: End of an Era?
Introduction: If you look at the early days of this blog, when web scalability was still in its heady bloom of youth, many of the articles had to do with leveraging MySQL and memcached . Exciting times. Shard MySQL to handle high write loads, cache objects in memcached to handle high read loads, and then write a lot of glue code to make it all work together. That was state of the art, that was how it was done. The architecture of many major sites still follow this pattern today, largely because with enough elbow grease, it works. This was a pre-cloud, relational database dominated world, built from parts scrounged from the remnants of enterprises and datacenters past. Twitter and Digg started in this era, but are evolving into something different, as scaling pressures increase and new purpose built technologies pop into being. With a little perspective, it's clear the MySQL+memcached era is passing. It will stick around for a while. Old technologies seldom fade away completely. Some still
2 0.19583477 927 high scalability-2010-10-26-Marrying memcached and NoSQL
Introduction: Memcached is one of the most common In-Memory cache implementation. It was originally developed by Danga Interactive for LiveJournal , but is now used by many other sites as a side cache to speed up read mostly operations. It gained popularity in the non-Java world, too, especially since it’s a language-neutral side cache for which few alternatives existed. As a side-cache, Memcache clients relies on the database as the system of record, The database is still used for write,update and complex query operations. Since the memcached specification includes no query operations, memcached is not a database alternative, unlike most of the NoSQL offerings. It also exclude memcache from being a real solution for write scalability. As a result of that many of the heavy sites started to move away from Memcache and replace it with other NoSQL alternatives as noted in a recent highscalability post MySQL And Memcached: End Of An Era? The transition away from memcached to NoSQL
3 0.17787756 360 high scalability-2008-08-04-A Bunch of Great Strategies for Using Memcached and MySQL Better Together
Introduction: The primero recommendation for speeding up a website is almost always to add cache and more cache. And after that add a little more cache just in case. Memcached is almost always given as the recommended cache to use. What we don't often hear is how to effectively use a cache in our own products. MySQL hosted two excellent webinars (referenced below) on the subject of how to deploy and use memcached. The star of the show, other than MySQL of course, is Farhan Mashraqi of Fotolog. You may recall we did an earlier article on Fotolog in Secrets to Fotolog's Scaling Success , which was one of my personal favorites. Fotolog, as they themselves point out, is probably the largest site nobody has ever heard of, pulling in more page views than even Flickr. Fotolog has 51 instances of memcached on 21 servers with 175G in use and 254G available. As a large successful photo-blogging site they have very demanding performance and scaling requirements. To meet those requirements they've developed a
4 0.1656552 729 high scalability-2009-10-28-And the winner is: MySQL or Memcached or Tokyo Tyrant?
Introduction: Matt, from the ever excellent MySQL Performance Blog , decided to run a test using a simple scenario drawn from his client experience in the gaming space. The scenario: read a row based on a primary key, update the row, write it to disk, and use the row to lookup another row. Matt ran three different tests explained in a series of three different articles: MySQL and MySQL + Memcached, Memcached Only , and Tokyo Tyrant . The lovingly compiled details along with many cool graphs are in the articles, but in general the lessons learned are: When memcached has enough memory (so records being accessed are in RAM), memcached + MySQL can provide a 10x performance boost over MySQL alone. When the RAM is too small and hot records, those being accessed a lot, aren't in RAM, or perhaps applications are doing a sequential scan of a table and the entire table isn't cached, then memcached won't be the big bang improvement you may be hoping for. When the database is removed and memcac
5 0.16404191 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.14616224 931 high scalability-2010-10-28-Notes from A NOSQL Evening in Palo Alto
10 0.12926373 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
11 0.12589729 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
12 0.12518479 806 high scalability-2010-04-08-Hot Scalability Links for April 8, 2010
13 0.12474294 920 high scalability-2010-10-15-Troubles with Sharding - What can we learn from the Foursquare Incident?
14 0.12394045 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
15 0.11693631 648 high scalability-2009-07-02-It Must be Crap on Relational Dabases Week
16 0.11196595 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
17 0.10898345 367 high scalability-2008-08-17-Strategy: Drop Memcached, Add More MySQL Servers
18 0.10566834 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
19 0.10544088 589 high scalability-2009-05-05-Drop ACID and Think About Data
20 0.10533115 1501 high scalability-2013-08-13-In Memoriam: Lavabit Architecture - Creating a Scalable Email Service
topicId topicWeight
[(0, 0.214), (1, 0.091), (2, -0.0), (3, -0.007), (4, 0.068), (5, 0.087), (6, -0.129), (7, -0.055), (8, 0.012), (9, -0.05), (10, -0.044), (11, 0.004), (12, -0.008), (13, 0.1), (14, 0.011), (15, -0.037), (16, -0.005), (17, -0.038), (18, -0.036), (19, -0.002), (20, -0.029), (21, 0.02), (22, 0.01), (23, 0.003), (24, 0.052), (25, 0.051), (26, 0.022), (27, 0.044), (28, 0.013), (29, -0.025), (30, -0.034), (31, 0.031), (32, 0.007), (33, 0.004), (34, -0.03), (35, -0.037), (36, -0.031), (37, 0.019), (38, 0.026), (39, 0.034), (40, 0.066), (41, 0.058), (42, -0.026), (43, -0.013), (44, -0.011), (45, 0.009), (46, 0.029), (47, -0.08), (48, -0.023), (49, -0.006)]
simIndex simValue blogId blogTitle
same-blog 1 0.97344267 785 high scalability-2010-02-26-MySQL and Memcached: End of an Era?
Introduction: If you look at the early days of this blog, when web scalability was still in its heady bloom of youth, many of the articles had to do with leveraging MySQL and memcached . Exciting times. Shard MySQL to handle high write loads, cache objects in memcached to handle high read loads, and then write a lot of glue code to make it all work together. That was state of the art, that was how it was done. The architecture of many major sites still follow this pattern today, largely because with enough elbow grease, it works. This was a pre-cloud, relational database dominated world, built from parts scrounged from the remnants of enterprises and datacenters past. Twitter and Digg started in this era, but are evolving into something different, as scaling pressures increase and new purpose built technologies pop into being. With a little perspective, it's clear the MySQL+memcached era is passing. It will stick around for a while. Old technologies seldom fade away completely. Some still
2 0.8284651 770 high scalability-2010-02-03-NoSQL Means Never Having to Store Blobs Again
Introduction: Morgan Tocker has an awesome article and comment thread in the MySQL Performance Blog about When should you store serialized objects in the database? Before the NoSQL age is was very common to simulate schemalessness by storing blobs in MySQL. Sharding was implemented by running multiple MySQL instances and spreading writes across them. While not ideal for the purpose, developers felt comfortable with MySQL. They knew how to install it, back it up, replicate it, in short:Â they knew how to make it work. Yet they also needed to store objects without the penalty of joins. Searches and aggregate queries were handled by indexes kept in separate tables, this offloaded the fast path to objects. This all made perfect sense. Usually we just want stuff to work and going with what you know is often the best path to that goal. And what we have known is MySQL. All the different pros and cons of this approach are covered wonderfully in the post. But the world has changed. With the same goal
3 0.80651802 1025 high scalability-2011-04-16-The NewSQL Market Breakdown
Introduction: Matt Aslett from the 451 group created a term called “NewSQL ”. On the definition of NewSQL, Aslett writes: “NewSQL” is our shorthand for the various new scalable/high performance SQL database vendors. We have previously referred to these products as ‘ScalableSQL’ to differentiate them from the incumbent relational database products. Since this implies horizontal scalability, which is not necessarily a feature of all the products, we adopted the term ‘NewSQL’ in the new report. And to clarify, like NoSQL, NewSQL is not to be taken too literally: the new thing about the NewSQL vendors is the vendor, not the SQL. As with NoSQL, under the NewSQL umbrella you can see various providers, with various solutions. I think these can be divided into several sub-types: New MySQL storage engines . These give MySQL users the same programming interface, but scale very well. You can Xeround or Akiban in this field. The good part is that you still use MySQL, but on the downside it’s n
4 0.79369509 927 high scalability-2010-10-26-Marrying memcached and NoSQL
Introduction: Memcached is one of the most common In-Memory cache implementation. It was originally developed by Danga Interactive for LiveJournal , but is now used by many other sites as a side cache to speed up read mostly operations. It gained popularity in the non-Java world, too, especially since it’s a language-neutral side cache for which few alternatives existed. As a side-cache, Memcache clients relies on the database as the system of record, The database is still used for write,update and complex query operations. Since the memcached specification includes no query operations, memcached is not a database alternative, unlike most of the NoSQL offerings. It also exclude memcache from being a real solution for write scalability. As a result of that many of the heavy sites started to move away from Memcache and replace it with other NoSQL alternatives as noted in a recent highscalability post MySQL And Memcached: End Of An Era? The transition away from memcached to NoSQL
Introduction: Michael Stonebraker sure knows how to stir up a storm. Unlike for others, that doesn't make him a troll in my mind, he's way too accomplished in the field to be that, but he does have a bit of Barnum & Bailey in him, which serves to get the discussion flowing, and that's a good thing. A lot of previously hidden wisdom and passion unlocks, which we'll try to capture here. This disturbance in the force is over OldSQL vs NoSQL vs NewSQL . Warning, these are not crisp categories, there's leakage all over the place, watch your step: OldSQL (Oracle, MySQL, etc) refers to what some want to term as legacy relational database like MySQL, that don't scale out horizontally with aplomb. NoSQL (CouchDB, Redis, Cassandra, HBase, MongoDB, Riak, Neo4j, etc) refers to, well, a collection of technologies that aren't OldSQL, these often are designed to scale out horizontally, aren't on ACID, and use schemaless non-relational datamodels. NewSQL (Xeround, Clustrix, NimbusDB, GenieDB, Sc
6 0.76816338 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
7 0.75966007 729 high scalability-2009-10-28-And the winner is: MySQL or Memcached or Tokyo Tyrant?
8 0.75796062 1080 high scalability-2011-07-15-Stuff The Internet Says On Scalability For July 15, 2011
9 0.74369633 935 high scalability-2010-11-05-Hot Scalability Links For November 5th, 2010
10 0.74253404 648 high scalability-2009-07-02-It Must be Crap on Relational Dabases Week
11 0.73260862 931 high scalability-2010-10-28-Notes from A NOSQL Evening in Palo Alto
12 0.72898567 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
13 0.72455937 779 high scalability-2010-02-16-Seven Signs You May Need a NoSQL Database
14 0.7099759 860 high scalability-2010-07-17-Hot Scalability Links for July 17, 2010
15 0.70650172 736 high scalability-2009-11-04-Damn, Which Database do I Use Now?
16 0.70393628 192 high scalability-2007-12-25-IBMer Says LAMP Can't Scale
17 0.70369887 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
18 0.70049906 670 high scalability-2009-08-05-Anti-RDBMS: A list of distributed key-value stores
19 0.70036292 1097 high scalability-2011-08-12-Stuff The Internet Says On Scalability For August 12, 2011
20 0.69966316 1642 high scalability-2014-05-02-Stuff The Internet Says On Scalability For May 2nd, 2014
topicId topicWeight
[(1, 0.104), (2, 0.229), (30, 0.02), (31, 0.196), (61, 0.116), (77, 0.043), (79, 0.117), (85, 0.034), (94, 0.053)]
simIndex simValue blogId blogTitle
1 0.94098806 1651 high scalability-2014-05-20-It's Networking. In Space! Or How E.T. Will Phone Home.
Introduction: What will the version of the Internet that follows us to the stars look like? Yes, people are really thinking seriously about this sort of thing. Specifically the InterPlanetary Networking Special Interest Group (IPNSIG). Ansible-like faster-than-light communication it isn't. There's no magical warp drive. Nor is a network of telepaths acting as a 'verse spanning telegraph system. It's more mundane than that. And in many ways more interesting as it's sort of like the old Internet on steroids, the one that was based on on UUCP and dial-up connections, but over vastly longer distances and with much longer delays : The Interplanetary Internet (based on IPN, also called InterPlaNet) is a conceived computer network in space, consisting of a set of network nodes which can communicate with each other.[1][2] Communication would be greatly delayed by the great interplanetary distances, so the IPN needs a new set of protocols and technology that are tolerant to large delays and
2 0.92681891 207 high scalability-2008-01-10-Sharding with Cookie-Based Session Storage
Introduction: In a recent project, I utilized RoR's cookie-based session storage to shard geographically distinct user groups. My technique for doing so was unique and, although it was a premature optimization, it is none-the-less an idea worth exploring.
3 0.91987926 368 high scalability-2008-08-17-Wuala - P2P Online Storage Cloud
Introduction: How do you design a reliable distributed file system when the expected availability of the individual nodes are only ~1/5? That is the case for P2P systems. Dominik Grolimund, the founder of a Swiss startup Caleido will show you how! They have launched Wuala , the social online storage service which scales as new nodes join the P2P network. The goal of Wua.la is to provide distributed online storage that is: large scalable reliable secure by harnessing the idle resources of participating computers. This challenge is an old dream of computer science. In fact as Andrew Tanenbaum wrote in 1995: "The design of a world-wide, fully transparent distributed filesystem fot simultaneous use by millions of mobile and frequently disconnected users is left as an exercise for the reader" After three years of research and development at at ETH Zurich, the Swiss Federal Institute of Technology on a distributed storage system, Caleido is ready to unveil the resu
4 0.90938562 615 high scalability-2009-06-01-HotPads on AWS
Introduction: HotPads abandoned our managed hosting in December and took the leap over to EC2 and its siblings. The presentation has a lot of detail on costs and other things to watch out for, so if you're currently planning your "cloud" architecture, you'll find some of this really helpful.
same-blog 5 0.90350068 785 high scalability-2010-02-26-MySQL and Memcached: End of an Era?
Introduction: If you look at the early days of this blog, when web scalability was still in its heady bloom of youth, many of the articles had to do with leveraging MySQL and memcached . Exciting times. Shard MySQL to handle high write loads, cache objects in memcached to handle high read loads, and then write a lot of glue code to make it all work together. That was state of the art, that was how it was done. The architecture of many major sites still follow this pattern today, largely because with enough elbow grease, it works. This was a pre-cloud, relational database dominated world, built from parts scrounged from the remnants of enterprises and datacenters past. Twitter and Digg started in this era, but are evolving into something different, as scaling pressures increase and new purpose built technologies pop into being. With a little perspective, it's clear the MySQL+memcached era is passing. It will stick around for a while. Old technologies seldom fade away completely. Some still
6 0.90277356 1255 high scalability-2012-06-01-Stuff The Internet Says On Scalability For June 1, 2012
7 0.87797403 294 high scalability-2008-04-01-How to update video views count effectively?
8 0.87087542 702 high scalability-2009-09-11-The interactive cloud
9 0.83252543 1020 high scalability-2011-04-12-Caching and Processing 2TB Mozilla Crash Reports in memory with Hazelcast
10 0.83129573 892 high scalability-2010-09-02-Distributed Hashing Algorithms by Example: Consistent Hashing
11 0.82887977 589 high scalability-2009-05-05-Drop ACID and Think About Data
12 0.82649195 1233 high scalability-2012-04-25-The Anatomy of Search Technology: blekko’s NoSQL database
13 0.82625759 849 high scalability-2010-06-28-VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
14 0.82589221 1256 high scalability-2012-06-04-OpenFlow-SDN is Not a Silver Bullet for Network Scalability
15 0.8257851 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
16 0.82571775 1428 high scalability-2013-03-22-Stuff The Internet Says On Scalability For March 22, 2013
17 0.82495934 1106 high scalability-2011-08-26-Stuff The Internet Says On Scalability For August 26, 2011
18 0.82487267 517 high scalability-2009-02-21-Google AppEngine - A Second Look
19 0.82425618 1460 high scalability-2013-05-17-Stuff The Internet Says On Scalability For May 17, 2013
20 0.82386404 1131 high scalability-2011-10-24-StackExchange Architecture Updates - Running Smoothly, Amazon 4x More Expensive