high_scalability high_scalability-2010 high_scalability-2010-877 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: I can’t even count the number of times that I’ve heard this phrase: “don’t worry about scaling your web application, worry about visitor (or customer) acquisition.” My response to this is always that you don’t need to choose one or the other, you can do both! In this post, I’m going to go over some of the strategies I’ve used to architect web applications for scalability, right from the start of the design process, in such a way that I’m prepared to scale when I need to, but not forced into doing so before its necessary. Easing the transition from small scale to large scale can be made much easier by choosing the right technologies and implementing the right coding patterns up front. You can read the full store here .
sentIndex sentText sentNum sentScore
1 I can’t even count the number of times that I’ve heard this phrase: “don’t worry about scaling your web application, worry about visitor (or customer) acquisition. [sent-1, score-1.524]
2 ” My response to this is always that you don’t need to choose one or the other, you can do both! [sent-2, score-0.422]
3 In this post, I’m going to go over some of the strategies I’ve used to architect web applications for scalability, right from the start of the design process, in such a way that I’m prepared to scale when I need to, but not forced into doing so before its necessary. [sent-3, score-1.671]
4 Easing the transition from small scale to large scale can be made much easier by choosing the right technologies and implementing the right coding patterns up front. [sent-4, score-2.037]
wordName wordTfidf (topN-words)
[('easing', 0.346), ('storehere', 0.325), ('worry', 0.301), ('phrase', 0.258), ('right', 0.231), ('visitor', 0.225), ('forced', 0.205), ('prepared', 0.194), ('heard', 0.182), ('choosing', 0.177), ('transition', 0.176), ('count', 0.169), ('coding', 0.164), ('scale', 0.146), ('implementing', 0.145), ('choose', 0.141), ('architect', 0.139), ('patterns', 0.138), ('strategies', 0.136), ('easier', 0.116), ('customer', 0.115), ('technologies', 0.105), ('response', 0.096), ('start', 0.087), ('web', 0.085), ('made', 0.082), ('need', 0.081), ('full', 0.08), ('going', 0.079), ('times', 0.078), ('small', 0.074), ('always', 0.073), ('ca', 0.072), ('process', 0.07), ('post', 0.07), ('design', 0.069), ('read', 0.064), ('number', 0.064), ('scaling', 0.063), ('go', 0.061), ('applications', 0.058), ('even', 0.056), ('scalability', 0.054), ('large', 0.053), ('much', 0.053), ('way', 0.051), ('used', 0.049), ('application', 0.048), ('one', 0.031)]
simIndex simValue blogId blogTitle
same-blog 1 1.0 877 high scalability-2010-08-12-Designing Web Applications for Scalability
Introduction: I can’t even count the number of times that I’ve heard this phrase: “don’t worry about scaling your web application, worry about visitor (or customer) acquisition.” My response to this is always that you don’t need to choose one or the other, you can do both! In this post, I’m going to go over some of the strategies I’ve used to architect web applications for scalability, right from the start of the design process, in such a way that I’m prepared to scale when I need to, but not forced into doing so before its necessary. Easing the transition from small scale to large scale can be made much easier by choosing the right technologies and implementing the right coding patterns up front. You can read the full store here .
2 0.14104052 1172 high scalability-2012-01-10-A Perfect Fifth of Notes on Scalability
Introduction: Jeremiah Peschka with a great a set of Notes on Scalability , just in case you do reach your wildest expectations of success: Build it to Break . Plan for the fact that everything you make is going to break. Design in layers that are independent and redundant. Everything is a Feature . Your application is a set of features created by a series of conscious choices made by considering trade-offs. Scale Out, Not Up . Purchasing more hardware is easier than coding and managing horizontal resources. Buy More Storage . Large numbers of smaller, faster drives have more IOPS than fewer, larger drives. You’re Going to Do It Wrong . Be prepared to iterate on your ideas. You will make mistakes. Be prepared to re-write code and to quickly move on to the next idea. Please read the original article for a much more expansive treatment.
3 0.11949639 840 high scalability-2010-06-10-The Four Meta Secrets of Scaling at Facebook
Introduction: Aditya Agarwal, Director of Engineering at Facebook, gave an excellent Scale at Facebook talk that covers their architecture, but the talk is really more about how to scale an organization by preserving the best parts of its culture. The key take home of the talk is: You can get the code right, you can get the products right, but you need to get the culture right first. If you don't get the culture right then your company won't scale. This leads into the four meta secrets of scaling at Facebook: Scaling takes Iteration Don't Over Design Choose the right tool for the job, but realize that your choice comes with overhead. Get the culture right. Move Fast - break things. Huge Impact - small teams. Be bold - innovate. Some Background Facebook is big : 400 million active users; users spend an average of 20 minutes a day; 5 billion pieces of content (status updates, comments, likes, photo uploads, video uploads, chat messages, inbox messages, group events, f
4 0.10746185 96 high scalability-2007-09-18-Amazon Architecture
Introduction: This is a wonderfully informative Amazon update based on Joachim Rohde's discovery of an interview with Amazon's CTO. You'll learn about how Amazon organizes their teams around services, the CAP theorem of building scalable systems, how they deploy software, and a lot more. Many new additions from the ACM Queue article have also been included. Amazon grew from a tiny online bookstore to one of the largest stores on earth. They did it while pioneering new and interesting ways to rate, review, and recommend products. Greg Linden shared is version of Amazon's birth pangs in a series of blog articles Site: http://amazon.com Information Sources Early Amazon by Greg Linden How Linux saved Amazon millions Interview Werner Vogels - Amazon's CTO Asynchronous Architectures - a nice summary of Werner Vogels' talk by Chris Loosley Learning from the Amazon technology platform - A Conversation with Werner Vogels Werner Vogels' Weblog - building scalable and robus
5 0.10349065 892 high scalability-2010-09-02-Distributed Hashing Algorithms by Example: Consistent Hashing
Introduction: Consistent Hashing is a specific implementation of hashing that is well suited for many of today’s web-scale load balancing problems. Specifically, it can be seen in use in various caching solutions like Memcached and is applicable to NoSQL solutions as well. Consistent Hashing is used particularly because it provides a solution for the typical “hashcode mod n” method of distributing keys across a series of servers. It does this by allowing servers to be added or removed without significantly upsetting the distribution of keys, nor does it require that all keys be rehashed to accommodate the change in the number of servers. You can read the full store here .
6 0.098808974 37 high scalability-2007-07-28-Product: Web Log Storming
7 0.09836147 149 high scalability-2007-11-12-Scaling Using Cache Farms and Read Pooling
8 0.098293506 100 high scalability-2007-09-26-Use a CDN to Instantly Improve Your Website's Performance by 20% or More
9 0.092750736 872 high scalability-2010-08-05-Pairing NoSQL and Relational Data Storage: MySQL with MongoDB
10 0.091804795 400 high scalability-2008-10-01-The Pattern Bible for Distributed Computing
11 0.086157836 1056 high scalability-2011-06-09-Retrospect on recent AWS outage and Resilient Cloud-Based Architecture
12 0.084092632 950 high scalability-2010-11-30-NoCAP – Part III – GigaSpaces clustering explained..
13 0.083404407 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
14 0.080830969 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
15 0.079979867 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
16 0.07602533 915 high scalability-2010-10-05-Sponsored Post: Box.net, Wiredrive, Joyent, DeviantART, CloudSigma, ManageEngine, Site24x7
17 0.075363353 1413 high scalability-2013-02-27-42 Monster Problems that Attack as Loads Increase
19 0.073312648 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
20 0.073196985 1440 high scalability-2013-04-15-Scaling Pinterest - From 0 to 10s of Billions of Page Views a Month in Two Years
topicId topicWeight
[(0, 0.131), (1, 0.03), (2, 0.012), (3, -0.016), (4, 0.027), (5, -0.022), (6, -0.041), (7, -0.011), (8, -0.024), (9, -0.005), (10, -0.018), (11, 0.018), (12, -0.054), (13, 0.02), (14, 0.01), (15, -0.053), (16, 0.046), (17, -0.043), (18, 0.013), (19, 0.029), (20, 0.004), (21, 0.005), (22, 0.003), (23, -0.011), (24, 0.031), (25, -0.029), (26, -0.027), (27, -0.027), (28, 0.026), (29, 0.023), (30, 0.008), (31, -0.007), (32, 0.074), (33, 0.038), (34, -0.048), (35, 0.028), (36, -0.061), (37, -0.038), (38, 0.021), (39, -0.053), (40, 0.037), (41, -0.013), (42, -0.047), (43, -0.027), (44, 0.006), (45, 0.023), (46, 0.008), (47, -0.062), (48, -0.016), (49, -0.052)]
simIndex simValue blogId blogTitle
same-blog 1 0.98105377 877 high scalability-2010-08-12-Designing Web Applications for Scalability
Introduction: I can’t even count the number of times that I’ve heard this phrase: “don’t worry about scaling your web application, worry about visitor (or customer) acquisition.” My response to this is always that you don’t need to choose one or the other, you can do both! In this post, I’m going to go over some of the strategies I’ve used to architect web applications for scalability, right from the start of the design process, in such a way that I’m prepared to scale when I need to, but not forced into doing so before its necessary. Easing the transition from small scale to large scale can be made much easier by choosing the right technologies and implementing the right coding patterns up front. You can read the full store here .
2 0.74416661 1172 high scalability-2012-01-10-A Perfect Fifth of Notes on Scalability
Introduction: Jeremiah Peschka with a great a set of Notes on Scalability , just in case you do reach your wildest expectations of success: Build it to Break . Plan for the fact that everything you make is going to break. Design in layers that are independent and redundant. Everything is a Feature . Your application is a set of features created by a series of conscious choices made by considering trade-offs. Scale Out, Not Up . Purchasing more hardware is easier than coding and managing horizontal resources. Buy More Storage . Large numbers of smaller, faster drives have more IOPS than fewer, larger drives. You’re Going to Do It Wrong . Be prepared to iterate on your ideas. You will make mistakes. Be prepared to re-write code and to quickly move on to the next idea. Please read the original article for a much more expansive treatment.
3 0.70058012 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
Introduction: This is a guest posting by Marty Abbott and Michael Fisher, authors of The Art of Scalability . I'm still reading their book and will have an interview with them a little later. If 2010 is the year that you’ve decided to kickoff your startup or if you’ve already got something off the ground and are expecting double or triple digit growth, this list is for you. We all want the attention of user s to achieve viral growth but as many can attest , too much attention can bring a startup to its knees. If you’ve used Twitter for any amount of time you’re sure to have seen the “Fail Whale”, which is so often seen that it has its own fan club . Take a look at the graph below from Compete.com showing Twitter’s unique visitors. One can argue that limitations in the product offering have as much to do with the flattening of growth over the past six months as does the availability , but it’s hard to beli
4 0.69640827 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
Introduction: This is a guest repost by Venkatesh CM at Architecture Issues Scaling Web Applications . I will cover architecture issues that show up while scaling and performance tuning large scale web application in this blog. Lets start by defining few terms to create common understanding and vocabulary. Later on I will go through different issues that pop-up while scaling web application like Architecture bottlenecks Scaling Database CPU Bound Application IO Bound Application Determining optimal thread pool size of an web application will be covered in next blog. Performance Term performance of web application is used to mean several things. Most developers are primarily concerned with are response time and scalability. Response Time Is the time taken by web application to process request and return response. Applications should respond to requests (response time) within acceptable duration. If application is taking beyond the acceptable time, it is said to
5 0.69433033 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
Introduction: Too often software design patterns are overlooked by network and application delivery network architects but these patterns are often equally applicable to addressing a broad range of architectural challenges in the application delivery tier of the data center. By Lori Mac Vittie, F5 Networks The “ High Scalability ” blog is fast becoming one of my favorite reads. Last week did not disappoint with a post highlighting a set of scalability design patterns that was, apparently, inspired by yet another High Scalability post on “ 6 Ways to Kill Your Servers: Learning to Scale the Hard Way. ” Credit:Michael Chow/azcentral.com This particular post caught my attention primarily because although I’ve touched on many of these patterns in the past, I’ve never thought to call them what they are: scalability patterns. That’s probably a side-effect of forgetting that building an architecture of any kind is at its core computer science and thus
6 0.68607253 921 high scalability-2010-10-18-NoCAP
8 0.666192 250 high scalability-2008-02-17-Web Accelerators - snake oil or miracle remedy?
9 0.65849817 702 high scalability-2009-09-11-The interactive cloud
10 0.65645558 185 high scalability-2007-12-13-Is premature scalation a real disease?
11 0.65269208 1087 high scalability-2011-07-26-Web 2.0 Killed the Middleware Star
12 0.6521762 684 high scalability-2009-08-18-Real World Web: Performance & Scalability
13 0.65126866 549 high scalability-2009-03-26-Performance - When do I start worrying?
14 0.64270878 407 high scalability-2008-10-10-The Art of Capacity Planning: Scaling Web Resources
15 0.64094162 384 high scalability-2008-09-16-EE-Appserver Clustering OR Terracota OR Coherence OR something else?
16 0.63421434 340 high scalability-2008-06-06-Economies of Non-Scale
17 0.6330421 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
18 0.62724268 330 high scalability-2008-05-27-Should Twitter be an All-You-Can-Eat Buffet or a Vending Machine?
20 0.62152183 747 high scalability-2009-11-26-What I'm Thankful For on Thanksgiving
topicId topicWeight
[(1, 0.103), (2, 0.273), (17, 0.262), (61, 0.224)]
simIndex simValue blogId blogTitle
1 0.91522509 199 high scalability-2008-01-01-S3 for image storing
Introduction: Hi all, Has anyone got any experience with using Amazon S3 as an uploaded photo store? I'm writing a website that I need to keep as low budget as possible, and I'm investigating solutions for storing uploaded photos from users - not too many, probably in the low thousands. The site is commercial so I'm straying away from the Flickrs of the world. S3 seems to offer a solution but I'd like to hear from those who have used it before. Thanks Andy
2 0.88910133 631 high scalability-2009-06-15-Large-scale Graph Computing at Google
Introduction: To continue the graph theme Google has got into the act and released information on Pregel . Pregel does not appear to be a new type of potato chip. Pregel is instead a scalable infrastructure... ...to mine a wide range of graphs. In Pregel, programs are expressed as a sequence of iterations. In each iteration, a vertex can, independently of other vertices, receive messages sent to it in the previous iteration, send messages to other vertices, modify its own and its outgoing edges' states, and mutate the graph's topology. Currently, Pregel scales to billions of vertices and edges, but this limit will keep expanding. Pregel's applicability is harder to quantify, but so far we haven't come across a type of graph or a practical graph computing problem which is not solvable with Pregel. It computes over large graphs much faster than alternatives, and the application programming interface is easy to use. Implementing PageRank, for example, takes only about 15 lines of code. Developers
3 0.87426502 956 high scalability-2010-12-08-How To Get Experience Working With Large Datasets
Introduction: I think I have been lucky that several of the projects I been worked on have exposed me to having to manage large volumes of data. The largest dataset was probably at MailChannels , though Livedoor.com also had some sizeable data for their books store and department store. Most of the pain with Livedoor’s data was from it being in Japanese. Other than that, it was pretty static. This was similar to the data I worked with at the BBC. You would be surprised at how much data can be involved with a single episode of a TV show. With any in-house generated data the update size and frequency is much less dramatic, even if the data is being regularly pumped in from 3rd parties. Those Humans The real fun comes when the public (that’s you guys) are generating data to be pumped into the system. MailChannels’ work with email, which is human generated (lies! 95% is actually from spambots). Humans are unpredictable. They suddenly all get excited about the same thing at the same time, they are
4 0.85790277 1467 high scalability-2013-05-30-Google Finds NUMA Up to 20% Slower for Gmail and Websearch
Introduction: When you have a large population of servers you have both the opportunity and the incentive to perform interesting studies. Authors from Google and the University of California in Optimizing Google’s Warehouse Scale Computers: The NUMA Experience conducted such a study, taking a look at how jobs run on clusters of machines using a NUMA architecture. Since NUMA is common on server class machines it's a topic of general interest for those looking to maximize machine utilization across clusters. Some of the results are surprising: The methodology of how to attribute such fine performance variations to NUMA effects within such a complex system is perhaps more interesting than the results themselves. Well worth reading just for that story. The performance swing due to NUMA is up to 15% on AMD Barcelona for Gmail backend and 20% on Intel Westmere for Web-search frontend. Memory locality is not always King. Because of the interaction between NUMA and cache sharing/contention it
5 0.85547543 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 =
same-blog 6 0.85235626 877 high scalability-2010-08-12-Designing Web Applications for Scalability
7 0.85203135 506 high scalability-2009-02-03-10 More Rules for Even Faster Websites
8 0.79956722 685 high scalability-2009-08-20-Dependency Injection and AOP frameworks for .NET
9 0.79527819 1225 high scalability-2012-04-09-Why My Slime Mold is Better than Your Hadoop Cluster
10 0.79001737 322 high scalability-2008-05-19-Conference: Infoscale 2008 in Italy (June 4-6)
11 0.78613192 427 high scalability-2008-10-22-Server load balancing architectures, Part 2: Application-level load balancing
12 0.78182244 564 high scalability-2009-04-10-counting # of views, calculating most-least viewed
13 0.77761251 637 high scalability-2009-06-24-Habits of Highly Scalable Web Applications
14 0.77738011 150 high scalability-2007-11-12-Slashdot Architecture - How the Old Man of the Internet Learned to Scale
15 0.77524966 1287 high scalability-2012-07-20-Stuff The Internet Says On Scalability For July 20, 2012
16 0.77504086 1393 high scalability-2013-01-24-NoSQL Parody: say No! No! and No!
17 0.77438277 501 high scalability-2009-01-25-Where do I start?
18 0.77066797 1538 high scalability-2013-10-28-Design Decisions for Scaling Your High Traffic Feeds
19 0.7704488 99 high scalability-2007-09-23-HA for switches
20 0.77044213 332 high scalability-2008-05-28-Job queue and search engine