high_scalability high_scalability-2009 high_scalability-2009-679 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: AFK Partners has release what they feel are the Best Practices for Scalability : Asynchronous - Use asynchronous communication when possible. Swim Lanes – Create fault isolated “swim lanes” of hardware by customer segmentation. Cache - Make use of cache at multiple layers. Monitoring - Understand your application’s performance from a customer’s perspective. Replication - Replicate databases for recovery as well as to off load reads to multiple instances. Sharding - Split the application and databases by service and / or by customer using a modulus. Use Few RDBMS Features – Use the OLTP database as a persistent storage device as much as possible. Slow Roll – Roll out new code versions slowly, to a small subset of your servers without bringing the entire site down. Load & Performance Testing – Test the performance of the application version before it goes into production. Capacity Planning / Scalability Summits – Know how much capacity you h
sentIndex sentText sentNum sentScore
1 AFK Partners has release what they feel are the Best Practices for Scalability : Asynchronous - Use asynchronous communication when possible. [sent-1, score-0.348]
2 Swim Lanes – Create fault isolated “swim lanes” of hardware by customer segmentation. [sent-2, score-0.454]
3 Cache - Make use of cache at multiple layers. [sent-3, score-0.165]
4 Monitoring - Understand your application’s performance from a customer’s perspective. [sent-4, score-0.078]
5 Replication - Replicate databases for recovery as well as to off load reads to multiple instances. [sent-5, score-0.365]
6 Sharding - Split the application and databases by service and / or by customer using a modulus. [sent-6, score-0.425]
7 Use Few RDBMS Features – Use the OLTP database as a persistent storage device as much as possible. [sent-7, score-0.198]
8 Slow Roll – Roll out new code versions slowly, to a small subset of your servers without bringing the entire site down. [sent-8, score-0.505]
9 Load & Performance Testing – Test the performance of the application version before it goes into production. [sent-9, score-0.171]
10 Capacity Planning / Scalability Summits – Know how much capacity you have on all tiers and services in your system. [sent-10, score-0.263]
11 Rollback – Always have the ability to rollback a code release. [sent-11, score-0.235]
12 Root Cause Analysis - Ensure you have a learning culture that is evident by utilizing Root Cause Analysis to find and fix the real cause of issues. [sent-12, score-0.833]
13 Quality From The Beginning – Quality can’t be tested into a product, it must be designed in from the beginning. [sent-13, score-0.111]
14 This is just a quick summary, more details on their site. [sent-14, score-0.087]
wordName wordTfidf (topN-words)
[('swim', 0.425), ('cause', 0.241), ('customer', 0.226), ('afk', 0.226), ('thebest', 0.195), ('lanes', 0.184), ('evident', 0.169), ('rollback', 0.158), ('utilizing', 0.156), ('tiers', 0.147), ('partners', 0.143), ('isolated', 0.135), ('slowly', 0.128), ('oltp', 0.124), ('roll', 0.121), ('capacity', 0.116), ('subset', 0.116), ('replicate', 0.115), ('rdbms', 0.113), ('culture', 0.113), ('tested', 0.111), ('bringing', 0.111), ('versions', 0.107), ('databases', 0.106), ('persistent', 0.103), ('root', 0.101), ('recovery', 0.099), ('split', 0.097), ('practices', 0.097), ('device', 0.095), ('site', 0.094), ('application', 0.093), ('planning', 0.093), ('fault', 0.093), ('summary', 0.091), ('asynchronous', 0.088), ('communication', 0.087), ('quick', 0.087), ('release', 0.087), ('feel', 0.086), ('multiple', 0.085), ('quality', 0.083), ('use', 0.08), ('learning', 0.078), ('performance', 0.078), ('code', 0.077), ('fix', 0.076), ('reads', 0.075), ('analysis', 0.074), ('ensure', 0.073)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000001 679 high scalability-2009-08-11-13 Scalability Best Practices
Introduction: AFK Partners has release what they feel are the Best Practices for Scalability : Asynchronous - Use asynchronous communication when possible. Swim Lanes – Create fault isolated “swim lanes” of hardware by customer segmentation. Cache - Make use of cache at multiple layers. Monitoring - Understand your application’s performance from a customer’s perspective. Replication - Replicate databases for recovery as well as to off load reads to multiple instances. Sharding - Split the application and databases by service and / or by customer using a modulus. Use Few RDBMS Features – Use the OLTP database as a persistent storage device as much as possible. Slow Roll – Roll out new code versions slowly, to a small subset of your servers without bringing the entire site down. Load & Performance Testing – Test the performance of the application version before it goes into production. Capacity Planning / Scalability Summits – Know how much capacity you h
2 0.14590502 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
3 0.14403191 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
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
5 0.10894909 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
8 0.098342963 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability
9 0.098122038 1314 high scalability-2012-08-30-Dramatically Improving Performance by Debugging Brutally Complex Prolems
11 0.095232375 753 high scalability-2009-12-21-Hot Holiday Scalability Links for 2009
12 0.091250546 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
13 0.085897312 572 high scalability-2009-04-16-Paper: The End of an Architectural Era (It’s Time for a Complete Rewrite)
14 0.083922207 240 high scalability-2008-02-05-Handling of Session for a site running from more than 1 data center
15 0.082613148 1209 high scalability-2012-03-14-The Azure Outage: Time Is a SPOF, Leap Day Doubly So
16 0.081756607 840 high scalability-2010-06-10-The Four Meta Secrets of Scaling at Facebook
18 0.080911435 1 high scalability-2007-07-06-Start Here
19 0.080592223 381 high scalability-2008-09-08-Guerrilla Capacity Planning and the Law of Universal Scalability
20 0.080261588 911 high scalability-2010-09-30-More Troubles with Caching
topicId topicWeight
[(0, 0.158), (1, 0.04), (2, -0.027), (3, -0.038), (4, 0.009), (5, -0.01), (6, 0.022), (7, -0.047), (8, -0.015), (9, -0.018), (10, -0.027), (11, 0.001), (12, -0.051), (13, 0.031), (14, 0.016), (15, -0.05), (16, 0.069), (17, -0.016), (18, 0.012), (19, 0.041), (20, 0.025), (21, 0.003), (22, -0.006), (23, 0.009), (24, -0.038), (25, 0.021), (26, -0.057), (27, -0.003), (28, 0.062), (29, 0.036), (30, 0.014), (31, 0.013), (32, 0.032), (33, -0.005), (34, 0.022), (35, 0.04), (36, -0.045), (37, 0.03), (38, -0.003), (39, 0.037), (40, -0.049), (41, -0.079), (42, 0.019), (43, 0.022), (44, 0.014), (45, -0.028), (46, 0.021), (47, 0.01), (48, -0.037), (49, 0.026)]
simIndex simValue blogId blogTitle
same-blog 1 0.95914495 679 high scalability-2009-08-11-13 Scalability Best Practices
Introduction: AFK Partners has release what they feel are the Best Practices for Scalability : Asynchronous - Use asynchronous communication when possible. Swim Lanes – Create fault isolated “swim lanes” of hardware by customer segmentation. Cache - Make use of cache at multiple layers. Monitoring - Understand your application’s performance from a customer’s perspective. Replication - Replicate databases for recovery as well as to off load reads to multiple instances. Sharding - Split the application and databases by service and / or by customer using a modulus. Use Few RDBMS Features – Use the OLTP database as a persistent storage device as much as possible. Slow Roll – Roll out new code versions slowly, to a small subset of your servers without bringing the entire site down. Load & Performance Testing – Test the performance of the application version before it goes into production. Capacity Planning / Scalability Summits – Know how much capacity you h
2 0.77814585 1367 high scalability-2012-12-05-5 Ways to Make Cloud Failure Not an Option
Introduction: With cloud SLAs generally being worth what you don't pay for them, what can you do to protect yourself? Sean Hull in AirBNB didn’t have to fail has some solid advice on how to deal with outages: Use Redundancy . Make database and webserver tiers redundant using multi-az or alternately read-replicas. Have a browsing only mode . Give users a read-only version of your site. Users may not even notice failures as they will only see problems when they need to perform a write operation. Web Applications need Feature Flags . Build in the ability to turn off and on major parts of your site and flip the switch when problems arise. Consider Netflix’s Simian . By randomly causing outages in your application you can continually test your failover and redundancy infrastructure. Use multiple clouds . Use Redundant Arrays of Inexpensive Clouds as a way of surviving outages in any one particular cloud. None of these are easy and it's worth considering that your application may
3 0.74020922 398 high scalability-2008-09-30-Scalability Worst Practices
Introduction: Brian Zimmer, architect at travel startup Yapta, highlights some worst practices jeopardizing the growth and scalability of a system: * The Golden Hammer. Forcing a particular technology to work in ways it was not intended is sometimes counter-productive. Using a database to store key-value pairs is one example. Another example is using threads to program for concurrency. * Resource Abuse. Manage the availability of shared resources because when they fail, by definition, their failure is experienced pervasively rather than in isolation. For example, connection management to the database through a thread pool. * Big Ball of Mud. Failure to manage dependencies inhibits agility and scalability. * Everything or Something. In both code and application dependency management, the worst practice is not understanding the relationships and formulating a model to facilitate their management. Failure to enforce diligent control is a contributing scalability inhibiter. * Forgetting to che
4 0.73642862 235 high scalability-2008-02-02-The case against ORM Frameworks in High Scalability Architectures
Introduction: Let me begin by saying that I have used and continue to use various ORM frameworks such as hibernate, ibatis, propel and activerecord in applications and websites that have a user base ranging from a couple hundred to 500k users. Especially for projects that have to be up and running in a short duration of time, ORM frameworks significantly reduce the effort required to manipulate and persist OOP objects by providing time saving facilities such as automatically generated model objects, integrated unit testing, secure variable substitution, etc. Hibernate even supports horizontal data partitioning via Hibernate Shards. However, the lay of the land is significantly different in the rarefied space occupied by applications needing to support millions of users. Profiling an application at this level and paying particular attention to the operations needed to move data to and from the database, it becomes evident that a significant portion of the operations are API related, whereby t
5 0.71379483 331 high scalability-2008-05-27-eBay Architecture
Introduction: Update 2: EBay's Randy Shoup spills the secrets of how to service hundreds of millions of users and over two billion page views a day in Scalability Best Practices: Lessons from eBay on InfoQ. The practices: Partition by Function, Split Horizontally, Avoid Distributed Transactions, Decouple Functions Asynchronously, Move Processing To Asynchronous Flows, Virtualize At All Levels, Cache Appropriately. Update: eBay Serves 5 Billion API Calls Each Month . Aren't we seeing more and more traffic driven by mashups composed on top of open APIs? APIs are no longer a bolt on, they are your application. Architecturally that argues for implementing your own application around the same APIs developers and users employ. Who hasn't wondered how eBay does their business? As one of the largest most loaded websites in the world, it can't be easy. And the subtitle of the presentation hints at how creating such a monster system requires true engineering: Striking a balance between site stabilit
6 0.70806003 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
7 0.67973316 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability
8 0.67871267 189 high scalability-2007-12-21-Strategy: Limit Result Sets
10 0.67016983 344 high scalability-2008-06-09-FaceStat's Rousing Tale of Scaling Woe and Wisdom Won
11 0.66841012 1041 high scalability-2011-05-15-Building a Database remote availability site
12 0.66114509 321 high scalability-2008-05-17-WebSphere Commerce High Availability and Performance Configurations
13 0.65319717 659 high scalability-2009-07-20-A Scalability Lament
14 0.64922583 151 high scalability-2007-11-12-a8cjdbc - Database Clustering via JDBC
15 0.64869183 1171 high scalability-2012-01-09-The Etsy Saga: From Silos to Happy to Billions of Pageviews a Month
16 0.64642632 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
17 0.64596695 1336 high scalability-2012-10-09-Batoo JPA - The new JPA Implementation that runs over 15 times faster...
18 0.64585614 614 high scalability-2009-06-01-Guess How Many Users it Takes to Kill Your Site?
20 0.6407271 384 high scalability-2008-09-16-EE-Appserver Clustering OR Terracota OR Coherence OR something else?
topicId topicWeight
[(1, 0.169), (2, 0.24), (10, 0.053), (39, 0.184), (40, 0.074), (77, 0.01), (79, 0.163)]
simIndex simValue blogId blogTitle
1 0.92527044 901 high scalability-2010-09-16-How Can the Large Hadron Collider Withstand One Petabyte of Data a Second?
Introduction: Why is there something rather than nothing? That's the kind of question the Large Hadron Collider in CERN is hopefully poised to answer. And what is the output of this beautiful 17-mile long, 6 billion dollar wabi-sabish proton smashing machine? Data. Great heaping torrents of Grand Canyon sized data. 15 million gigabytes every year. That's 1000 times the information printed in books every year. It's so much data 10,000 scientists will use a grid of 80,000+ computers , in 300 computer centers , in 50 different countries just to help make sense of it all. How will all this data be collected, transported, stored, and analyzed? It turns out, using what amounts to sort of Internet of Particles instead of an Internet of Things. Two good articles have recently shed some electro-magnetic energy in the human visible spectrum on the IT aspects of the collider: LHC computing grid pushes petabytes of data, beats expectations by John Timmer on Ars Technica and an overview of the Br
same-blog 2 0.91205692 679 high scalability-2009-08-11-13 Scalability Best Practices
Introduction: AFK Partners has release what they feel are the Best Practices for Scalability : Asynchronous - Use asynchronous communication when possible. Swim Lanes – Create fault isolated “swim lanes” of hardware by customer segmentation. Cache - Make use of cache at multiple layers. Monitoring - Understand your application’s performance from a customer’s perspective. Replication - Replicate databases for recovery as well as to off load reads to multiple instances. Sharding - Split the application and databases by service and / or by customer using a modulus. Use Few RDBMS Features – Use the OLTP database as a persistent storage device as much as possible. Slow Roll – Roll out new code versions slowly, to a small subset of your servers without bringing the entire site down. Load & Performance Testing – Test the performance of the application version before it goes into production. Capacity Planning / Scalability Summits – Know how much capacity you h
3 0.90815389 1145 high scalability-2011-11-18-Stuff The Internet Says On Scalability For November 18, 2011
Introduction: Every kiss begins with HighScalability: Amazon and the secret to life: 42 ; 10,240 cores Many quatloos worth of quotable quotes: @alesroubicek : State kills scalability @cincura_net : Wrong. *Shared* state kills scalability. @kpshea : When I think "cloud" computing, I imagine the gaseous Star Trek blob that ate red blood cells (your sensitive data). @kotobuki : I'm interested in scalability of personal fabrication. How to 'scale' in batch production stages will be a key, but still there are barriers. @simonraikallen : The two rules of scalability testing: (1) The bottleneck is always the database (2) You can never predict what the bottleneck will be. @mastachand : Spot on Post by @storagebod about PetaByte-Scale storage. it's not only about scaling. It's about "Simple Scalability" ( http://www.storagebod.com/wordpress/?p=930 ) @mschopman : don't forget about scalability, better response times due to shorter distances, ability to add
4 0.906537 842 high scalability-2010-06-16-Hot Scalability Links for June 16, 2010
Introduction: You're Doing it Wrong by Poul-Henning Kamp. Don't look so guilty, he's not talking about you know what, he's talking about writing high-performance server programs: Not just wrong as in not perfect, but wrong as in wasting half, or more, of your performance. What good is an O(log2(n)) algorithm if those operations cause page faults and slow disk operations? For most relevant datasets an O(n) or even an O(n^2) algorithm, which avoids page faults, will run circles around it. A Microsoft Windows Azure primer: the basics by Peter Bright. Nice article explaining the basics of Azure and how it compares to Google and Amazon. A call to change the name from NoSQL to Postmodern Databases . Interesting idea, but the problem is the same one I have for Postmodern Art, when is it? I always feel like I'm in the post-post modern period, yet for art it's really in the early 1900s. Let's save future developers from this existential time crisis. Constructions from Dots and Lines by M
5 0.8971532 1498 high scalability-2013-08-07-RAFT - In Search of an Understandable Consensus Algorithm
Introduction: If like many humans you've found even Paxos Made Simple a bit difficult to understand, you might enjoy RAFT as described in In Search of an Understandable Consensus Algorithm by Stanford's Diego Ongaro and John Ousterhout. The video presentation of the paper is given by John Ousterhout . Both the paper and the video are delightfully accessible. mcherm has a good summary of the paper: A consensus algorithm is: a cluster of servers should record a series of records ("log entries") in response to requests from clients of the cluster. (It may also take action based on those entries.) It does so in a way that guarantees that the responses seen by clients of the cluster will be consistent EVEN in the face of servers crashing in unpredictable ways (but not loosing data that was synched to disk), and networks introducing unpredictable delays or communication blockages. Here's what Raft does. First, it elects a leader, then the leader records the master version of the log, t
6 0.88414353 653 high scalability-2009-07-08-Servers Component - How to choice and build perfect server
7 0.86382914 1148 high scalability-2011-11-29-DataSift Architecture: Realtime Datamining at 120,000 Tweets Per Second
8 0.85720468 585 high scalability-2009-04-29-How to choice and build perfect server
9 0.85321343 63 high scalability-2007-08-09-Lots of questions for high scalability - high availability
10 0.85221654 636 high scalability-2009-06-23-Learn How to Exploit Multiple Cores for Better Performance and Scalability
11 0.8495627 879 high scalability-2010-08-12-Think of Latency as a Pseudo-permanent Network Partition
12 0.84878623 1286 high scalability-2012-07-18-Strategy: Kill Off Multi-tenant Instances with High CPU Stolen Time
13 0.84796846 865 high scalability-2010-07-27-A Metric A$$-Ton of Joe Stump: The Cloud is Cheaper than Bare Metal
14 0.84734267 1276 high scalability-2012-07-04-Top Features of a Scalable Database
15 0.84670806 1492 high scalability-2013-07-17-How do you create a 100th Monkey software development culture?
16 0.84496331 415 high scalability-2008-10-15-Need help with your Hadoop deployment? This company may help!
19 0.84281653 309 high scalability-2008-04-23-Behind The Scenes of Google Scalability
20 0.84258324 15 high scalability-2007-07-16-Blog: MySQL Performance Blog - Everything about MySQL Performance.