high_scalability high_scalability-2007 high_scalability-2007-185 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Update 3: InfoQ's Big Architecture Up Front - A Case of Premature Scalaculation? twines several different threads on the topic together into a fine noose. Update 2: Kevin says the biggest problems he sees with startups is they need to scale their backend (no, the other one). Update: My bad. It's hard to sell scalability so just forget it. The premise of Startups and The Problem Of Premature Scalaculation and Don’t scale: 99.999% uptime is for Wal-Mart is that you shouldn't spend precious limited resources worrying about scaling before you've first implemented the functionality that will make you successful enough to have scaling problems in the first place. It's kind of an embodied life force model of system creation. Energy is scarce so any parasites siphoning off energy must be hunted down and destroyed so the body has its best chance of survival. Is this really how it works? If I ever believed this I certainly don't believe it anymore. The world has c
sentIndex sentText sentNum sentScore
1 Update 2: Kevin says the biggest problems he sees with startups is they need to scale their backend (no, the other one). [sent-3, score-0.156]
2 It's hard to sell scalability so just forget it. [sent-5, score-0.078]
3 The premise of Startups and The Problem Of Premature Scalaculation and Don’t scale: 99. [sent-6, score-0.114]
4 999% uptime is for Wal-Mart is that you shouldn't spend precious limited resources worrying about scaling before you've first implemented the functionality that will make you successful enough to have scaling problems in the first place. [sent-7, score-0.906]
5 It's kind of an embodied life force model of system creation. [sent-8, score-0.132]
6 Energy is scarce so any parasites siphoning off energy must be hunted down and destroyed so the body has its best chance of survival. [sent-9, score-0.762]
7 If I ever believed this I certainly don't believe it anymore. [sent-11, score-0.111]
8 Thanks to many books and papers on how to scale the knowledge of scaling isn't the scarce precious resource it once was. [sent-13, score-0.761]
9 It's no longer knowledge tightly held by a cabal of experts until Nicolas Cage flies in and pries it out of their grasping dessicated fingers. [sent-14, score-0.464]
10 Not only has knowledge dissemination improved, but so have our tools. [sent-16, score-0.257]
11 At one time building a scalable system up front would have required buying and configuring a truck load of servers, building out a data center, configuring a spider's web of networks, and bootstrapping an equally nasty storage network. [sent-18, score-0.867]
12 While most of us toil away in anonymity and scaling problems are just a fond dream, when the webosphere does find you it does so with a crush. [sent-21, score-0.613]
13 Usually doing the right thing isn't harder if you know what is the right thing to do. [sent-26, score-0.234]
14 Could they have recovered from the opportunity lost of grabbing the iron when it's hot and when potential customers are interested? [sent-28, score-0.345]
15 Has most of the risk associated with up front scalability design been squeezed out? [sent-31, score-0.304]
16 Or have times changed and does doing the simplest thing that could possibly work now include worrying about scaling up front? [sent-33, score-0.622]
wordName wordTfidf (topN-words)
[('premature', 0.291), ('precious', 0.213), ('front', 0.19), ('scarce', 0.182), ('worrying', 0.166), ('knowledge', 0.157), ('fond', 0.14), ('grabbing', 0.14), ('toil', 0.14), ('configuring', 0.135), ('cabal', 0.132), ('embodied', 0.132), ('gbs', 0.132), ('hunted', 0.132), ('parasites', 0.132), ('energy', 0.13), ('scaling', 0.128), ('anonymity', 0.126), ('likeamazon', 0.126), ('thing', 0.117), ('changed', 0.115), ('spider', 0.114), ('premise', 0.114), ('squeezed', 0.114), ('recovered', 0.111), ('believed', 0.111), ('implemented', 0.11), ('bootstrapping', 0.107), ('nasty', 0.105), ('truck', 0.105), ('destroyed', 0.101), ('dissemination', 0.1), ('tightly', 0.098), ('simplest', 0.096), ('iron', 0.094), ('equally', 0.09), ('avoided', 0.088), ('origin', 0.088), ('blue', 0.088), ('seriously', 0.088), ('body', 0.085), ('uptime', 0.082), ('kevin', 0.082), ('books', 0.081), ('problems', 0.079), ('doubt', 0.079), ('sell', 0.078), ('sees', 0.077), ('held', 0.077), ('dream', 0.074)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 185 high scalability-2007-12-13-Is premature scalation a real disease?
Introduction: Update 3: InfoQ's Big Architecture Up Front - A Case of Premature Scalaculation? twines several different threads on the topic together into a fine noose. Update 2: Kevin says the biggest problems he sees with startups is they need to scale their backend (no, the other one). Update: My bad. It's hard to sell scalability so just forget it. The premise of Startups and The Problem Of Premature Scalaculation and Don’t scale: 99.999% uptime is for Wal-Mart is that you shouldn't spend precious limited resources worrying about scaling before you've first implemented the functionality that will make you successful enough to have scaling problems in the first place. It's kind of an embodied life force model of system creation. Energy is scarce so any parasites siphoning off energy must be hunted down and destroyed so the body has its best chance of survival. Is this really how it works? If I ever believed this I certainly don't believe it anymore. The world has c
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
3 0.11511909 1331 high scalability-2012-10-02-An Epic TripAdvisor Update: Why Not Run on the Cloud? The Grand Experiment.
Introduction: This is a guest post by Shawn Hsiao , Luke Massa , and Victor Luu . Shawn runs TripAdvisor ’s Technical Operations team, Luke and Victor interned on his team this past summer. This post is introduced by Andy Gelfond , TripAdvisor’s head of engineering. It's been a little over a year since our last post about the TripAdvisor architecture . It has been an exciting year. Our business and team continues to grow, we are now an independent public company, and we have continued to keep/scale our development process and culture as we have grown - we still run dozens of independent teams, and each team continues to work across the entire stack. All that has changed are the numbers: 56M visitors per month 350M+ pages requests a day 120TB+ of warehouse data running on a large Hadoop cluster, and quickly growing We also had a very successful college intern program that brought on over 60 interns this past summer, all who were quickly on boarded and doing the same kind of work a
4 0.10568662 691 high scalability-2009-08-31-Squarespace Architecture - A Grid Handles Hundreds of Millions of Requests a Month
Introduction: I first heard an enthusiastic endorsement of Squarespace streaming from the ubiquitous Leo Laporte on one of his many Twit Live shows. Squarespace as a fully hosted, completely managed environment for creating and maintaining a website, blog or portfolio was of interest to me because they promise scalability and this site doesn't have enough of that. But sadly, since they don't offer a link preserving Drupal import our relationship was not meant to be. When a fine reader of High Scalability, Brian Egge, (and all my readers are thrifty, brave, and strong) asked me how Squarespace scaled I said I didn't know, but I would try and find out. I emailed Squarespace a few questions and founder Anthony Casalena and Director of Technical Operations Rolando Berrios were kind enough to reply in some detail. The questions were both from Brian and myself. Answers can be found below. Two things struck me most about Squarespace's approach: They based their system on a memory grid, in this
5 0.10305678 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.
6 0.09989395 840 high scalability-2010-06-10-The Four Meta Secrets of Scaling at Facebook
7 0.097453788 313 high scalability-2008-05-02-Friends for Sale Architecture - A 300 Million Page View-Month Facebook RoR App
10 0.091196448 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
13 0.086762995 672 high scalability-2009-08-06-An Unorthodox Approach to Database Design : The Coming of the Shard
14 0.083123393 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
18 0.078922085 1439 high scalability-2013-04-12-Stuff The Internet Says On Scalability For April 12, 2013
19 0.077621117 126 high scalability-2007-10-20-Should you build your next website using 3tera's grid OS?
20 0.077609554 1431 high scalability-2013-03-29-Stuff The Internet Says On Scalability For March 29, 2013
topicId topicWeight
[(0, 0.155), (1, 0.056), (2, -0.006), (3, 0.01), (4, 0.01), (5, -0.051), (6, -0.057), (7, 0.01), (8, -0.038), (9, -0.01), (10, -0.023), (11, 0.018), (12, 0.002), (13, 0.033), (14, 0.044), (15, -0.015), (16, 0.03), (17, 0.023), (18, 0.001), (19, 0.047), (20, -0.006), (21, 0.013), (22, -0.003), (23, -0.026), (24, -0.007), (25, -0.04), (26, 0.015), (27, -0.001), (28, -0.021), (29, 0.035), (30, 0.024), (31, 0.01), (32, 0.008), (33, 0.026), (34, 0.012), (35, -0.004), (36, -0.028), (37, 0.007), (38, 0.048), (39, -0.02), (40, -0.013), (41, -0.026), (42, -0.006), (43, -0.033), (44, -0.044), (45, 0.017), (46, -0.03), (47, 0.009), (48, 0.012), (49, -0.065)]
simIndex simValue blogId blogTitle
same-blog 1 0.97557813 185 high scalability-2007-12-13-Is premature scalation a real disease?
Introduction: Update 3: InfoQ's Big Architecture Up Front - A Case of Premature Scalaculation? twines several different threads on the topic together into a fine noose. Update 2: Kevin says the biggest problems he sees with startups is they need to scale their backend (no, the other one). Update: My bad. It's hard to sell scalability so just forget it. The premise of Startups and The Problem Of Premature Scalaculation and Don’t scale: 99.999% uptime is for Wal-Mart is that you shouldn't spend precious limited resources worrying about scaling before you've first implemented the functionality that will make you successful enough to have scaling problems in the first place. It's kind of an embodied life force model of system creation. Energy is scarce so any parasites siphoning off energy must be hunted down and destroyed so the body has its best chance of survival. Is this really how it works? If I ever believed this I certainly don't believe it anymore. The world has c
2 0.81879401 1613 high scalability-2014-03-17-Intuitively Showing How To Scale a Web Application Using a Coffee Shop as an Example
Introduction: This is a guest repost by Sriram Devadas , Engineer at Vistaprint, Web platform group. A fun and well written analogy of how to scale web applications using a familiar coffee shop as an example. No coffee was harmed during the making of this post. I own a small coffee shop. My expense is proportional to resources 100 square feet of built up area with utilities, 1 barista, 1 cup coffee maker. My shop's capacity Serves 1 customer at a time, takes 3 minutes to brew a cup of coffee, a total of 5 minutes to serve a customer. Since my barista works without breaks and the German made coffee maker never breaks down, my shop's maximum throughput = 12 customers per hour. Web server Customers walk away during peak hours. We only serve one customer at a time. There is no space to wait. I upgrade shop. My new setup is better! Expenses Same area and utilities, 3 baristas, 2 cup coffee maker, 2 chairs Capacity 3 minutes to brew 2 cups of coffee, ~7 minutes to serv
Introduction: Update 2: Velocity 09: John Allspaw, 10+ Deploys Per Day: Dev and Ops Cooperation at Flickr . Insightful talk. Some highlights: Change is good if you can build tools and culture to lower the risk of change. Operations and developers need to become of one mind and respect each other. An automated infrastructure is the one tool you need most. Common source control. One step build. One step deploy. Don't be a pussy, deploy. Always ship trunk. Feature flags - don't branch code, make features runtime configurable in code. Dark launch - release data paths early without UI component. Shared metrics. Adaptive feedback to prioritize important features. IRC for communication for human context. Best solutions occur when dev and op work together and trust each other. Trust is earned by helping each other solve their problems. Look at what new features imply for operations, what can go wrong, and how to recover. Provide knobs and levers to help operations. Devs should have access to production
4 0.80763495 691 high scalability-2009-08-31-Squarespace Architecture - A Grid Handles Hundreds of Millions of Requests a Month
Introduction: I first heard an enthusiastic endorsement of Squarespace streaming from the ubiquitous Leo Laporte on one of his many Twit Live shows. Squarespace as a fully hosted, completely managed environment for creating and maintaining a website, blog or portfolio was of interest to me because they promise scalability and this site doesn't have enough of that. But sadly, since they don't offer a link preserving Drupal import our relationship was not meant to be. When a fine reader of High Scalability, Brian Egge, (and all my readers are thrifty, brave, and strong) asked me how Squarespace scaled I said I didn't know, but I would try and find out. I emailed Squarespace a few questions and founder Anthony Casalena and Director of Technical Operations Rolando Berrios were kind enough to reply in some detail. The questions were both from Brian and myself. Answers can be found below. Two things struck me most about Squarespace's approach: They based their system on a memory grid, in this
5 0.80359542 869 high scalability-2010-07-30-Hot Scalability Links for July 30, 2010
Introduction: Jeremy Zawodny, while performing data alchemy in the dungeons of Craigslist, stored 1,250,000,000 Key/Value Pairs in Redis on a 32GB Machine . Data sorting world record: 1 terabyte, 1 minute . The system has 52 computer nodes, each node is a commodity server with two quad-core processors, 24 gigabytes (GB) memory and sixteen 500 GB disks . It's not just hardware though, they also built a software that utilized all their CPU and RAM. Tweets of Gold: wm : I am really getting the sense that none of you yokels waxing profound about scalability actually has anything factual to say joestump : I think you can do things to *mitigate* pain points up front. You don't need to over-engineer, but it's not hard to look forward. danielcrenna : I love it when I check in debug code accidentally and it turns into a three day hunt for a major scalability problem joestump : Your post also makes me think of another phrase I say often: Scaling == Specialization. Bigger scale =
6 0.80187297 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
7 0.78979266 1172 high scalability-2012-01-10-A Perfect Fifth of Notes on Scalability
8 0.76765096 193 high scalability-2007-12-26-Finding an excellent LAMP developer
9 0.76563835 1366 high scalability-2012-12-03-Resiliency is the New Normal - A Deep Look at What It Means and How to Build It
10 0.76036894 130 high scalability-2007-10-24-Scaling Operations Saves Money and Scales Faster
11 0.75976694 142 high scalability-2007-11-05-Strategy: Diagonal Scaling - Don't Forget to Scale Out AND Up
12 0.74684179 1420 high scalability-2013-03-08-Stuff The Internet Says On Scalability For March 8, 2013
13 0.74514359 275 high scalability-2008-03-14-Problem: Mobbing the Least Used Resource Error
14 0.74139208 330 high scalability-2008-05-27-Should Twitter be an All-You-Can-Eat Buffet or a Vending Machine?
15 0.73920512 1379 high scalability-2012-12-31-Designing for Resiliency will be so 2013
16 0.73882079 1534 high scalability-2013-10-18-Stuff The Internet Says On Scalability For October 18th, 2013
17 0.7372669 1468 high scalability-2013-05-31-Stuff The Internet Says On Scalability For May 31, 2013
18 0.73494923 659 high scalability-2009-07-20-A Scalability Lament
20 0.72833639 863 high scalability-2010-07-22-How can we spark the movement of research out of the Ivory Tower and into production?
topicId topicWeight
[(1, 0.131), (2, 0.223), (10, 0.074), (30, 0.014), (61, 0.075), (66, 0.27), (79, 0.088), (85, 0.015), (94, 0.032)]
simIndex simValue blogId blogTitle
1 0.85845071 375 high scalability-2008-09-01-A Scalability checklist?
Introduction: Hi everyone, I'm researching on Scalability for a college paper, and found this site great, but it has too many tips, articles and the like, but I can't see a hierarchical organization of subjects, I would need something like a checklist of things or fields, or technologies to take into account when assesing scalability. So far I've identified these: - Hardware scalability: - scale out - scale up - Cache What types of cache are there? app-level, os-level, network-level, I/O-level? - Load Balancing - DB Clustering Am I missing something important? (I'm sure I am) I don't expect you to give a lecture here, but maybe point some things out, give me some useful links... Thanks!
same-blog 2 0.85821778 185 high scalability-2007-12-13-Is premature scalation a real disease?
Introduction: Update 3: InfoQ's Big Architecture Up Front - A Case of Premature Scalaculation? twines several different threads on the topic together into a fine noose. Update 2: Kevin says the biggest problems he sees with startups is they need to scale their backend (no, the other one). Update: My bad. It's hard to sell scalability so just forget it. The premise of Startups and The Problem Of Premature Scalaculation and Don’t scale: 99.999% uptime is for Wal-Mart is that you shouldn't spend precious limited resources worrying about scaling before you've first implemented the functionality that will make you successful enough to have scaling problems in the first place. It's kind of an embodied life force model of system creation. Energy is scarce so any parasites siphoning off energy must be hunted down and destroyed so the body has its best chance of survival. Is this really how it works? If I ever believed this I certainly don't believe it anymore. The world has c
3 0.84228504 622 high scalability-2009-06-08-Distribution of queries per second
Introduction: We need to measure the number of queries-per-second our site gets for capacity planning purposes. Obviously, we need to provision the site based on the peak QPS, not average QPS. There will always be some spikes in traffic, though, where for one particular second we get a really huge number of queries. It's ok if site performance slightly degrades during that time. So what I'd really like to do is estimate the *near* peak QPS based on average or median QPS. Near peak might be defined as the QPS that I get at the 95th percentile of the busiest seconds during the day. My guess is that this is similar to what ISPs do when they measure your bandwidth usage and then charge for usage over the 95th percentile. What we've done is analyzed our logs, counted the queries executed during each second during the day, sorted from the busiest seconds to the least busy ones, and graphed it. What you get is a histogram that steeply declines and flattens out near zero. Does anyone know if there is a
4 0.839293 130 high scalability-2007-10-24-Scaling Operations Saves Money and Scales Faster
Introduction: Jesse Robbins at O'Reily Radar has a nice post on how spending a little up front time on figuring out how to scale your operations process saves money on ops people and allows you to save time adding and upgrading servers. Adding, monitoring, and upgrading servers can get so incredibly screwed up that a herd of squirrels has to work overtime just to put out a release. Or it can be one button simple from your automated build system out to your servers. This is one area where "do the simplest thing that could possibly work" is a dumb idea and Jesse does a good job capturing the advantages of doing it right.
5 0.82231933 973 high scalability-2011-01-14-Stuff The Internet Says On Scalability For January 14, 2011
Introduction: Submitted for your reading pleasure... On the new year Twitter set a record with 6,939 Tweets Per Second (TPS). Cool video visualizing New Year's Eve Tweet data across the world. Marko Rodriguez in Memoirs of a Graph Addict: Despair to Redemption tells a stirring tale of how graph programming saved the world from certain destruction by realizing Aritstotle's dream of an eudaimonia-driven society. Could a relational database do that? The tools of the revolution can be found at tinkerprop.com , which describes a databases agnostic stack for working with property graphs, they include Blueprints - a property graph model interface; Pipes - a dataflow netowork using process grapphs; Gremlin - a graph based programming language; Rexster - a RESTful graph shell. The never never ending battle of good versus evil has nothing on programmers arguing about bracket policies or sync vs async programming models. In this node.js thread, I love async, but I can't code like this , the batt
8 0.77514571 283 high scalability-2008-03-18-Shared filesystem on EC2
9 0.77147794 684 high scalability-2009-08-18-Real World Web: Performance & Scalability
10 0.75141197 383 high scalability-2008-09-10-Shard servers -- go big or small?
11 0.73769844 406 high scalability-2008-10-08-Strategy: Flickr - Do the Essential Work Up-front and Queue the Rest
12 0.73310196 72 high scalability-2007-08-22-Wikimedia architecture
13 0.73184061 619 high scalability-2009-06-05-HotPads Shows the True Cost of Hosting on Amazon
14 0.73171109 1369 high scalability-2012-12-10-Switch your databases to Flash storage. Now. Or you're doing it wrong.
15 0.7311002 498 high scalability-2009-01-20-Product: Amazon's SimpleDB
16 0.73073775 1470 high scalability-2013-06-05-A Simple 6 Step Transition Guide for Moving Away from X to AWS
17 0.73025602 798 high scalability-2010-03-22-7 Secrets to Successfully Scaling with Scalr (on Amazon) by Sebastian Stadil
19 0.72912836 1291 high scalability-2012-07-25-Vertical Scaling Ascendant - How are SSDs Changing Architectures?
20 0.72886062 1209 high scalability-2012-03-14-The Azure Outage: Time Is a SPOF, Leap Day Doubly So