high_scalability high_scalability-2008 high_scalability-2008-330 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Om proposes one solution to the Twitter Problem is to limit followers to three square meals a day. The reasonable idea being that lower limits should mean fewer scaling problems. And as a kicker raising those limits is a good way to raise much needed revenue. Scoble thinks users should consume without limit and will drive to another buffet if all-you-can-eat privileges are revoked. The reasonable idea being that if an internet service can't solve internet scale problems then there's not much use for it. Dave says comp power users a top floor suite and shower them with free passes to the buffet. Let the good times roll! The reasonable idea being that power users help create popular restaurants, er, services in the first place and limiting them starves users and starved users won't come back. So, should web services like Twitter be a buffet, a fixed eight course fine dining experience, a small plate restaurant, a family style joint, or a vending machine? Or
sentIndex sentText sentNum sentScore
1 The reasonable idea being that lower limits should mean fewer scaling problems. [sent-2, score-0.259]
2 And as a kicker raising those limits is a good way to raise much needed revenue. [sent-3, score-0.207]
3 Scoble thinks users should consume without limit and will drive to another buffet if all-you-can-eat privileges are revoked. [sent-4, score-0.213]
4 The reasonable idea being that if an internet service can't solve internet scale problems then there's not much use for it. [sent-5, score-0.221]
5 The reasonable idea being that power users help create popular restaurants, er, services in the first place and limiting them starves users and starved users won't come back. [sent-8, score-0.326]
6 A stacker who loved potato salad was manageable. [sent-22, score-0.499]
7 We had plenty of potato salad and it was cheap and quick to make. [sent-23, score-0.324]
8 But if a stacker's favorite food was roast beef, that was trouble. [sent-27, score-0.692]
9 Not only is roast beef expensive, it comes in a limited supply because it has to be prepared ahead of time. [sent-28, score-0.871]
10 Once you ran out there was no more roast beef for the rest of the night. [sent-29, score-0.871]
11 Good roast beef takes hours to prepare, it must be planned for. [sent-30, score-0.871]
12 Stackers blow apart the finely balanced calculation of how much roast beef to make and the carving station is left trying to push the ham while apologizing for an embarrassing lack of roast beef. [sent-33, score-1.529]
13 As a person with serious stacker tendencies I try to remember the cost of things and keep a reasonable balance. [sent-41, score-0.28]
14 Eventually the restaurant had to limit the number of trips to the roast beef station to three a meal. [sent-43, score-1.183]
15 It's all-you-can-eat some would say so I should be able to eat all I can eat ! [sent-48, score-0.257]
16 Would it be fair to back a truck up to the restaurant and start loading up because that's part of your meal? [sent-50, score-0.289]
17 Is it fair to stuff your backpack with food on the way out? [sent-52, score-0.267]
18 In the end I agree with Scoble in that the power of the internet is having interesting conversations with interesting people about interesting topics. [sent-69, score-0.216]
19 Relationships should be subject to DDOS type limits, but not limits artificially out of proportion with a user's internet audience. [sent-76, score-0.212]
20 I don't know, but I would try to treat relationships more like potato salad than roast beef. [sent-84, score-1.039]
wordName wordTfidf (topN-words)
[('roast', 0.524), ('beef', 0.347), ('salad', 0.175), ('stacker', 0.175), ('stackers', 0.175), ('restaurant', 0.164), ('limits', 0.154), ('buffet', 0.149), ('potato', 0.149), ('relationships', 0.13), ('fair', 0.125), ('freemium', 0.106), ('meal', 0.106), ('reasonable', 0.105), ('eat', 0.098), ('food', 0.089), ('agree', 0.085), ('station', 0.084), ('friendfeed', 0.084), ('meat', 0.08), ('favorite', 0.079), ('protecting', 0.076), ('ugly', 0.073), ('conversations', 0.073), ('prepare', 0.068), ('limiting', 0.065), ('ddos', 0.064), ('limit', 0.064), ('customers', 0.063), ('would', 0.061), ('internet', 0.058), ('paid', 0.054), ('kicker', 0.053), ('apower', 0.053), ('backpack', 0.053), ('constitution', 0.053), ('depended', 0.053), ('followersto', 0.053), ('meals', 0.053), ('medieval', 0.053), ('shielded', 0.053), ('starved', 0.053), ('starves', 0.053), ('friends', 0.053), ('happy', 0.051), ('place', 0.05), ('plate', 0.05), ('om', 0.05), ('finely', 0.05), ('goldilocks', 0.05)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999988 330 high scalability-2008-05-27-Should Twitter be an All-You-Can-Eat Buffet or a Vending Machine?
Introduction: Om proposes one solution to the Twitter Problem is to limit followers to three square meals a day. The reasonable idea being that lower limits should mean fewer scaling problems. And as a kicker raising those limits is a good way to raise much needed revenue. Scoble thinks users should consume without limit and will drive to another buffet if all-you-can-eat privileges are revoked. The reasonable idea being that if an internet service can't solve internet scale problems then there's not much use for it. Dave says comp power users a top floor suite and shower them with free passes to the buffet. Let the good times roll! The reasonable idea being that power users help create popular restaurants, er, services in the first place and limiting them starves users and starved users won't come back. So, should web services like Twitter be a buffet, a fixed eight course fine dining experience, a small plate restaurant, a family style joint, or a vending machine? Or
2 0.1535532 1500 high scalability-2013-08-12-100 Curse Free Lessons from Gordon Ramsay on Building Great Software
Introduction: Gordon Ramsay is a world renowned chef with a surprising amount to say on software development. Well, he says it about cooking and running a restaurant, but it applies to software development too. You may have seen Gordon Ramsay on one of his many TV shows. Hell's Kitchen is a competition between chefs trying to win a dream job: head chef of their own high-end restaurant. On this show Ramsay is judge, jury, and executioner. And he chops off more than a few heads. Kitchen Nightmares is a show where Ramsay is called in by restaurant owners to help turn around their failing restaurants. On this show Ramsay is there to help. If you just watch Hell's Kitchen you will likely conclude Ramsay is one of the devil's own helpers ("ram" is the symbol of the devil and "say" means he speaks for the devil: Ramsay). Ramsay screams, yells, cusses, belittles, and throws tantrums even a 7 year old could learn from. Then he does it all over gain just for spite. In Hell's Kitchen there's no evidence a
Introduction: All in all this is still my favorite post and I still think it's an accurate vision of a future. Not everyone agrees, but I guess we'll see..."But it is not complicated. [There's] just a lot of it." \--Richard Feynmanon how the immense variety of the world arises from simple rules.Contents:Have We Reached the End of Scaling?Applications Become Black Boxes Using Markets to Scale and Control CostsLet's Welcome our Neo-Feudal OverlordsThe Economic Argument for the Ambient CloudWhat Will Kill the Cloud?The Amazing Collective Compute Power of the Ambient CloudUsing the Ambient Cloud as an Application RuntimeApplications as Virtual StatesConclusionWe have not yet begun to scale. The world is still fundamentally disconnected and for all our wisdom we are still in the earliest days of learning how to build truly large planet-scaling applications.Today 350 million users on Facebook is a lot of users and five million followers on Twitter is a lot of followers. This may seem like a lot now, but c
4 0.085897997 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
Introduction: "But it is not complicated. [There's] just a lot of it." \--Richard Feynmanon how the immense variety of the world arises from simple rules.Contents:Have We Reached the End of Scaling?Applications Become Black Boxes Using Markets to Scale and Control CostsLet's Welcome our Neo-Feudal OverlordsThe Economic Argument for the Ambient CloudWhat Will Kill the Cloud?The Amazing Collective Compute Power of the Ambient CloudUsing the Ambient Cloud as an Application RuntimeApplications as Virtual StatesConclusionWe have not yet begun to scale. The world is still fundamentally disconnected and for all our wisdom we are still in the earliest days of learning how to build truly large planet-scaling applications.Today 350 million users on Facebook is a lot of users and five million followers on Twitter is a lot of followers. This may seem like a lot now, but consider we have no planet wide applications yet. None.Tomorrow the numbers foreshadow a newCambrian explosionof connectivity that will look as
5 0.085838035 166 high scalability-2007-11-27-Solving the Client Side API Scalability Problem with a Little Game Theory
Introduction: Now that the internet has become defined as a mashup over a collection of service APIs, we have a little problem: for clients using APIs is a lot like drinking beer through a straw. You never get as much beer as you want and you get a headache after. But what if I've been a good boy and deserve a bigger straw? Maybe we can use game theory to model trust relationships over a life time of interactions over many different services and then give more capabilities/beer to those who have earned them? Let's say Twitter limits me to downloading only 20 tweets at a time through their API. But I want more. I may even want to do something so radical as download all my tweets. Of course Twitter can't let everyone do that. They would be swamped serving all this traffic and service would be denied. So Twitter does that rational thing and limits API access as a means of self protection. As does Google, Yahoo, Skynet , and everyone else. But when I hit the API limit I think, but hey it
6 0.081026383 837 high scalability-2010-06-07-Six Ways Twitter May Reach its Big Hairy Audacious Goal of One Billion Users
7 0.080101006 721 high scalability-2009-10-13-Why are Facebook, Digg, and Twitter so hard to scale?
8 0.078053847 517 high scalability-2009-02-21-Google AppEngine - A Second Look
9 0.074050039 639 high scalability-2009-06-27-Scaling Twitter: Making Twitter 10000 Percent Faster
10 0.072823644 1507 high scalability-2013-08-26-Reddit: Lessons Learned from Mistakes Made Scaling to 1 Billion Pageviews a Month
11 0.071196571 232 high scalability-2008-01-29-When things aren't scalable
12 0.069220997 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability
13 0.068324208 904 high scalability-2010-09-21-Playfish's Social Gaming Architecture - 50 Million Monthly Users and Growing
14 0.068293013 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
15 0.068007842 383 high scalability-2008-09-10-Shard servers -- go big or small?
16 0.067956999 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
17 0.0649895 1011 high scalability-2011-03-25-Did the Microsoft Stack Kill MySpace?
18 0.064625852 96 high scalability-2007-09-18-Amazon Architecture
19 0.064400643 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
20 0.063184358 299 high scalability-2008-04-07-Rumors of Signs and Portents Concerning Freeish Google Cloud
topicId topicWeight
[(0, 0.128), (1, 0.062), (2, 0.003), (3, -0.004), (4, 0.016), (5, -0.063), (6, -0.049), (7, 0.037), (8, 0.009), (9, -0.034), (10, -0.023), (11, 0.026), (12, -0.011), (13, 0.026), (14, 0.063), (15, -0.016), (16, 0.006), (17, 0.01), (18, 0.006), (19, 0.032), (20, -0.015), (21, -0.013), (22, 0.026), (23, 0.004), (24, -0.006), (25, -0.012), (26, 0.016), (27, -0.018), (28, 0.01), (29, -0.005), (30, 0.022), (31, -0.023), (32, 0.025), (33, 0.022), (34, -0.03), (35, 0.003), (36, -0.013), (37, 0.016), (38, -0.026), (39, -0.017), (40, 0.01), (41, -0.003), (42, -0.028), (43, 0.004), (44, -0.002), (45, 0.043), (46, 0.016), (47, -0.007), (48, -0.009), (49, 0.006)]
simIndex simValue blogId blogTitle
same-blog 1 0.96405721 330 high scalability-2008-05-27-Should Twitter be an All-You-Can-Eat Buffet or a Vending Machine?
Introduction: Om proposes one solution to the Twitter Problem is to limit followers to three square meals a day. The reasonable idea being that lower limits should mean fewer scaling problems. And as a kicker raising those limits is a good way to raise much needed revenue. Scoble thinks users should consume without limit and will drive to another buffet if all-you-can-eat privileges are revoked. The reasonable idea being that if an internet service can't solve internet scale problems then there's not much use for it. Dave says comp power users a top floor suite and shower them with free passes to the buffet. Let the good times roll! The reasonable idea being that power users help create popular restaurants, er, services in the first place and limiting them starves users and starved users won't come back. So, should web services like Twitter be a buffet, a fixed eight course fine dining experience, a small plate restaurant, a family style joint, or a vending machine? Or
2 0.86350632 363 high scalability-2008-08-12-Strategy: Limit The New, Not The Old
Introduction: One of the most popular and effective scalability strategies is to impose limits ( GAE Quotas , Fotolog , Facebook ) as a means of protecting a website against service destroying traffic spikes . Twitter will reportedly limit the number followers to 2,000 in order to thwart follow spam. This may also allow Twitter to make some bank by going freemium and charging for adding more followers. Agree or disagree with Twitter's strategies, the more interesting aspect for me is how do you introduce new policies into an already established ecosystem? One approach is the big bang. Introduce all changes at once and let everyone adjust. If users don't like it they can move on. The hope is, however, most users won't be impacted by the changes and that those who are will understand it's all for the greater good of their beloved service. Casualties are assumed, but the damage will probably be minor. Now in Twitter's case the people with the most followers tend to be o
3 0.84772909 166 high scalability-2007-11-27-Solving the Client Side API Scalability Problem with a Little Game Theory
Introduction: Now that the internet has become defined as a mashup over a collection of service APIs, we have a little problem: for clients using APIs is a lot like drinking beer through a straw. You never get as much beer as you want and you get a headache after. But what if I've been a good boy and deserve a bigger straw? Maybe we can use game theory to model trust relationships over a life time of interactions over many different services and then give more capabilities/beer to those who have earned them? Let's say Twitter limits me to downloading only 20 tweets at a time through their API. But I want more. I may even want to do something so radical as download all my tweets. Of course Twitter can't let everyone do that. They would be swamped serving all this traffic and service would be denied. So Twitter does that rational thing and limits API access as a means of self protection. As does Google, Yahoo, Skynet , and everyone else. But when I hit the API limit I think, but hey it
4 0.83475322 1500 high scalability-2013-08-12-100 Curse Free Lessons from Gordon Ramsay on Building Great Software
Introduction: Gordon Ramsay is a world renowned chef with a surprising amount to say on software development. Well, he says it about cooking and running a restaurant, but it applies to software development too. You may have seen Gordon Ramsay on one of his many TV shows. Hell's Kitchen is a competition between chefs trying to win a dream job: head chef of their own high-end restaurant. On this show Ramsay is judge, jury, and executioner. And he chops off more than a few heads. Kitchen Nightmares is a show where Ramsay is called in by restaurant owners to help turn around their failing restaurants. On this show Ramsay is there to help. If you just watch Hell's Kitchen you will likely conclude Ramsay is one of the devil's own helpers ("ram" is the symbol of the devil and "say" means he speaks for the devil: Ramsay). Ramsay screams, yells, cusses, belittles, and throws tantrums even a 7 year old could learn from. Then he does it all over gain just for spite. In Hell's Kitchen there's no evidence a
5 0.8015573 347 high scalability-2008-07-07-Five Ways to Stop Framework Fixation from Crashing Your Scaling Strategy
Introduction: If you've wondered why I haven't been posting lately it's because I've been on an amazing Beach's motorcycle tour of the Alps ( and , and , and , and , and , and , and , and ). My wife (Linda) and I rode two-up on a BMW 1200 GS through the alps in Germany, Austria, Switzerland, Italy, Slovenia, and Lichtenstein. The trip was more beautiful than I ever imagined. We rode challenging mountain pass after mountain pass, froze in the rain, baked in the heat, woke up on excellent Italian coffee, ate slice after slice of tasty apple strudel, drank dazzling local wines, smelled the fresh cut grass as the Swiss en masse cut hay for the winter feeding of their dairy cows, rode the amazing Munich train system, listened as cow bells tinkled like wind chimes throughout small valleys, drank water from a pure alpine spring on a blisteringly hot hike, watched local German folk dancers represent their regions, and had fun in the company of fellow riders. Magical. They say you'll ride more
6 0.79602927 344 high scalability-2008-06-09-FaceStat's Rousing Tale of Scaling Woe and Wisdom Won
8 0.78855574 1388 high scalability-2013-01-16-What if Cars Were Rented Like We Hire Programmers?
9 0.78568941 153 high scalability-2007-11-13-Friendster Lost Lead Because of a Failure to Scale
11 0.7754131 116 high scalability-2007-10-08-Lessons from Pownce - The Early Years
12 0.77030987 1515 high scalability-2013-09-11-Ten Lessons from GitHub’s First Year in 2008
13 0.76940179 659 high scalability-2009-07-20-A Scalability Lament
14 0.764543 976 high scalability-2011-01-20-75% Chance of Scale - Leveraging the New Scaleogenic Environment for Growth
15 0.76107961 758 high scalability-2010-01-11-Have We Reached the End of Scaling?
16 0.75926149 1490 high scalability-2013-07-12-Stuff The Internet Says On Scalability For July 12, 2013
17 0.75522804 1526 high scalability-2013-10-02-RFC 1925 - The Twelve (Timeless) Networking Truths
18 0.75485253 193 high scalability-2007-12-26-Finding an excellent LAMP developer
19 0.75331086 390 high scalability-2008-09-23-Scaling your cookie recipes
20 0.75140464 352 high scalability-2008-07-18-Robert Scoble's Rules for Successfully Scaling Startups
topicId topicWeight
[(1, 0.057), (2, 0.152), (10, 0.028), (27, 0.011), (40, 0.363), (49, 0.025), (61, 0.069), (79, 0.087), (85, 0.07), (94, 0.028)]
simIndex simValue blogId blogTitle
1 0.89661348 402 high scalability-2008-10-05-Paper: Scalability Design Patterns
Introduction: I have introduced pattern languages in my earlier post on The Pattern Bible for Distributed Computing . Achieving highest possible scalability is a complex combination of many factors. This PLoP 2007 paper presents a pattern language that can be used to make a system highly scalable. The Scalability Pattern Language introduced by Kanwardeep Singh Ahluwalia includes patterns to: Introduce Scalability Optimize Algorithm Add Hardware Add Parallelism Add Intra-Process Parallelism Add Inter-Porcess Parallelism Add Hybrid Parallelism Optimize Decentralization Control Shared Resources Automate Scalability
2 0.8950088 338 high scalability-2008-06-02-Total Cost of Ownership for different web development frameworks
Introduction: I would like to compile a comparison matrix on the total cost of ownership for .Net, Java, Lamp & Rails. Where should I start? Has anyone seen or know of a recent study on this subject?
3 0.87347233 1419 high scalability-2013-03-07-It's a VM Wasteland - A Near Optimal Packing of VMs to Machines Reduces TCO by 22%
Introduction: In Algorithm Design for Performance Aware VM Consolidation we learn some shocking facts (gambling in Casablanca?): Average server utilization in many data centers is low, estimated between 5% and 15%. This is wasteful because an idle server often consumes more than 50% of peak power. Surely that's just for old style datacenters? Nope. In Google data centers, workloads that are consolidated use only 50% of the processor cores. Every other processor core is left unused simply to ensure that performance does not degrade. It's a VM wasteland. The goal is to reduce waste by packing VMs onto machines without hurting performance or wasting resources. The idea is to select VMs that interfere the least with each other and places them together on the same server. It's a NP-Complete problem, but this paper describes a practical method that performs provably close to the optimal. Interestingly they can optimize for performance or power efficiency, so you can use different algorithm
4 0.86433482 860 high scalability-2010-07-17-Hot Scalability Links for July 17, 2010
Introduction: And by hot I also mean temperature. Summer has arrived. It's sizzling here in Silicon Valley. Thank you air conditioning! Scale the web by appointing a Crawler Czar? Tom Foremski has the idea that Google should open up their index so sites wouldn't have to endure the constant pounding by ravenous crawler bots. Don MacAskill of SmugMug estimates 50% of our web server CPU resources are spent serving crawlers. What a waste. How this would all work with real-time feeds, paid feeds (Twitter, movies, ...), etc. is unknown, but does it make sense for all that money to be spent on extracting the same data over and over again? Tweets of Gold: jamesurquhart : Key to applications is architecture. Key for infrastructure supporting archs is configurability. Configurability==features . tjake : People who choose their datastore based oh hearsay and not their own evaluation are doomed . b6n : No global lock ever goes unpunished. MichaelSurt
same-blog 5 0.84000063 330 high scalability-2008-05-27-Should Twitter be an All-You-Can-Eat Buffet or a Vending Machine?
Introduction: Om proposes one solution to the Twitter Problem is to limit followers to three square meals a day. The reasonable idea being that lower limits should mean fewer scaling problems. And as a kicker raising those limits is a good way to raise much needed revenue. Scoble thinks users should consume without limit and will drive to another buffet if all-you-can-eat privileges are revoked. The reasonable idea being that if an internet service can't solve internet scale problems then there's not much use for it. Dave says comp power users a top floor suite and shower them with free passes to the buffet. Let the good times roll! The reasonable idea being that power users help create popular restaurants, er, services in the first place and limiting them starves users and starved users won't come back. So, should web services like Twitter be a buffet, a fixed eight course fine dining experience, a small plate restaurant, a family style joint, or a vending machine? Or
6 0.83597946 1466 high scalability-2013-05-29-Amazon: Creating a Customer Utopia One Culture Hack at a Time
7 0.8115682 27 high scalability-2007-07-25-Product: 3 PAR REMOTE COPY
9 0.80059683 778 high scalability-2010-02-15-The Amazing Collective Compute Power of the Ambient Cloud
10 0.79093254 1471 high scalability-2013-06-06-Paper: Memory Barriers: a Hardware View for Software Hackers
11 0.75134379 1414 high scalability-2013-03-01-Stuff The Internet Says On Scalability For February 29, 2013
12 0.74314338 848 high scalability-2010-06-25-Hot Scalability Links for June 25, 2010
13 0.74146408 300 high scalability-2008-04-07-Scalr - Open Source Auto-scaling Hosting on Amazon EC2
14 0.73960286 879 high scalability-2010-08-12-Think of Latency as a Pseudo-permanent Network Partition
16 0.72154319 768 high scalability-2010-02-01-What Will Kill the Cloud?
17 0.68304253 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
18 0.67298096 1492 high scalability-2013-07-17-How do you create a 100th Monkey software development culture?
19 0.62359101 564 high scalability-2009-04-10-counting # of views, calculating most-least viewed
20 0.61781448 97 high scalability-2007-09-18-Session management in highly scalable web sites