high_scalability high_scalability-2008 high_scalability-2008-392 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: By Bhavin Turakhia CEO, Directi. Covers: * Why scalability is important. Viral marketing can result in instant success. With RSS/Ajax/SOA number of requests grow exponentially with user base. Goal is to build a web 2.0 app that can server millions of users with zero downtime. * Introduction to the variables. Scalability, performance, responsiveness, availability, downtime impact, cost, maintenance effort. * Introduction to the factors. Platform selection, hardware, application design, database architecture, deployment architecture, storage architecture, abuse prevention, monitoring mechanisms, etc. * Building our own scalable architecture in incremental steps: vertical scaling, vertical partitioning, horizontal scaling, horizontal partitioning, etc. First buy bigger. Then deploy each service on a separate node. Then increase the number of nudes and load balance. Deal with session management. Remove single points of failure. Use a shared nothing cluster. Choice of master-slave m
sentIndex sentText sentNum sentScore
1 With RSS/Ajax/SOA number of requests grow exponentially with user base. [sent-4, score-0.207]
2 0 app that can server millions of users with zero downtime. [sent-6, score-0.12]
3 Scalability, performance, responsiveness, availability, downtime impact, cost, maintenance effort. [sent-8, score-0.213]
4 Platform selection, hardware, application design, database architecture, deployment architecture, storage architecture, abuse prevention, monitoring mechanisms, etc. [sent-10, score-0.242]
5 * Building our own scalable architecture in incremental steps: vertical scaling, vertical partitioning, horizontal scaling, horizontal partitioning, etc. [sent-11, score-1.346]
6 Then increase the number of nudes and load balance. [sent-14, score-0.078]
7 Perform application sizing ongoingly to ensure optimal hardware utilization. [sent-29, score-0.337]
wordName wordTfidf (topN-words)
[('horizontal', 0.298), ('selection', 0.241), ('vertical', 0.229), ('bhavin', 0.213), ('turakhia', 0.213), ('introduction', 0.201), ('prevention', 0.184), ('architecture', 0.182), ('partitioning', 0.17), ('abuse', 0.169), ('sizing', 0.159), ('session', 0.155), ('viral', 0.143), ('responsiveness', 0.14), ('loosely', 0.133), ('exponentially', 0.129), ('zero', 0.12), ('ceo', 0.12), ('synchronous', 0.115), ('platform', 0.115), ('add', 0.114), ('cdns', 0.114), ('downtime', 0.11), ('incremental', 0.11), ('covers', 0.108), ('reverse', 0.107), ('mechanisms', 0.106), ('utilization', 0.105), ('maintenance', 0.103), ('steps', 0.103), ('instant', 0.099), ('marketing', 0.098), ('couple', 0.096), ('hardware', 0.092), ('remove', 0.091), ('optimal', 0.086), ('db', 0.084), ('serving', 0.081), ('number', 0.078), ('scaling', 0.078), ('buy', 0.077), ('object', 0.077), ('use', 0.075), ('grid', 0.074), ('goal', 0.074), ('deployment', 0.073), ('interface', 0.073), ('points', 0.073), ('impact', 0.073), ('choice', 0.072)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 392 high scalability-2008-09-24-Building a Scalable Architecture for Web Apps
Introduction: By Bhavin Turakhia CEO, Directi. Covers: * Why scalability is important. Viral marketing can result in instant success. With RSS/Ajax/SOA number of requests grow exponentially with user base. Goal is to build a web 2.0 app that can server millions of users with zero downtime. * Introduction to the variables. Scalability, performance, responsiveness, availability, downtime impact, cost, maintenance effort. * Introduction to the factors. Platform selection, hardware, application design, database architecture, deployment architecture, storage architecture, abuse prevention, monitoring mechanisms, etc. * Building our own scalable architecture in incremental steps: vertical scaling, vertical partitioning, horizontal scaling, horizontal partitioning, etc. First buy bigger. Then deploy each service on a separate node. Then increase the number of nudes and load balance. Deal with session management. Remove single points of failure. Use a shared nothing cluster. Choice of master-slave m
2 0.14180641 637 high scalability-2009-06-24-Habits of Highly Scalable Web Applications
Introduction: Nick Belhomme wrote up a excellent summary of a talk given by Eli White on building scalable web applications. Eli worked at digg.com and is now the PHP Community Manager & DevZone Editor-in-Chief at Zend Technologies. Eli takes us on a grand tour through various proven scaling strategies. On the trip you'll visit: What is scalable application design Tip 1: load balancing the webserver Tip 2: scaling from a single DB server to a Master-Slave setup Tip 3: Partitioning, Vertical DB Scaling Tip 4: Partitioning, horizontal DB Scaling Tip 5: Application Level Partitioning Tip 6: Caching to get around your database Resources
3 0.13548122 511 high scalability-2009-02-12-MySpace Architecture
Introduction: Update: Presentation: Behind the Scenes at MySpace.com . Dan Farino, Chief Systems Architect at MySpace shares details of some of MySpace's cool internal operations tools. MySpace.com is one of the fastest growing site on the Internet with 65 million subscribers and 260,000 new users registering each day. Often criticized for poor performance, MySpace has had to tackle scalability issues few other sites have faced. How did they do it? Site: http://myspace.com Information Sources Presentation: Behind the Scenes at MySpace.com Inside MySpace.com Platform ASP.NET 2.0 Windows IIS SQL Server What's Inside? 300 million users. Pushes 100 gigabits/second to the internet. 10Gb/sec is HTML content. 4,500+ web servers windows 2003/IIS 6.0/APS.NET. 1,200+ cache servers running 64-bit Windows 2003. 16GB of objects cached in RAM. 500+ database servers running 64-bit Windows and SQL Server 2005. MySpace processes 1.5 Billion page views per day and
4 0.13000591 948 high scalability-2010-11-24-Great Introductory Video on Scalability from Harvard Computer Science
Introduction: Professor David Malan gives a very good lecture on scalability for dynamic websites. It's not highly technical, it's an extension course, but it's a great introduction to a wide variety of topics. I really like his teaching style. He continually asks questions, prompts for input, and gives accessible explanations. Some of the topics covered: vertical scaling; horizontal scaling; PHP acceleration; load balancing: DNS, L7, sticky sessions, load balancers; caching; MySQL: replication, load balancing, partitioning, high availability. Watch it on Academic Earth This is one lecture in a series of 13 lectures on building dynamic websites. Students learn how to: build dynamic websites with Ajax and with Linux , Apache , MySQL , and PHP ( LAMP ); set up domain names with DNS ; structure pages with XHTML and CSS how to program in JavaScript and PHP ; configure Apache and MySQL ; design and query databases with SQL ; use Ajax with both XML and JSON ;
5 0.12444094 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
6 0.12077364 560 high scalability-2009-04-08-Learned lessons from the largest player (Flickr, YouTube, Google, etc)
7 0.11822151 18 high scalability-2007-07-16-Paper: MySQL Scale-Out by application partitioning
8 0.11668362 873 high scalability-2010-08-06-Hot Scalability Links for Aug 6, 2010
9 0.10813015 717 high scalability-2009-10-07-How to Avoid the Top 5 Scale-Out Pitfalls
10 0.10734809 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
11 0.10600219 602 high scalability-2009-05-17-Scaling Django Web Apps by Mike Malone
12 0.10334335 709 high scalability-2009-09-19-Space Based Programming in .NET
13 0.10295189 345 high scalability-2008-06-11-Pyshards aspires to build sharding toolkit for Python
14 0.10233555 96 high scalability-2007-09-18-Amazon Architecture
15 0.10034811 684 high scalability-2009-08-18-Real World Web: Performance & Scalability
16 0.100055 97 high scalability-2007-09-18-Session management in highly scalable web sites
17 0.098670244 754 high scalability-2009-12-22-Incremental deployment
18 0.098527536 1654 high scalability-2014-06-05-Cloud Architecture Revolution
19 0.097562872 331 high scalability-2008-05-27-eBay Architecture
20 0.096686184 6 high scalability-2007-07-11-Friendster Architecture
topicId topicWeight
[(0, 0.166), (1, 0.041), (2, -0.013), (3, -0.057), (4, -0.02), (5, 0.001), (6, -0.015), (7, -0.083), (8, -0.049), (9, 0.044), (10, -0.018), (11, 0.02), (12, -0.016), (13, 0.048), (14, -0.026), (15, -0.008), (16, 0.043), (17, 0.015), (18, 0.04), (19, 0.034), (20, 0.013), (21, 0.046), (22, -0.038), (23, -0.126), (24, -0.012), (25, -0.034), (26, 0.007), (27, -0.033), (28, 0.002), (29, 0.099), (30, 0.064), (31, -0.053), (32, -0.003), (33, -0.053), (34, -0.002), (35, -0.045), (36, -0.056), (37, -0.049), (38, 0.009), (39, -0.002), (40, 0.031), (41, -0.011), (42, -0.01), (43, -0.019), (44, 0.047), (45, 0.003), (46, -0.02), (47, 0.051), (48, -0.09), (49, -0.013)]
simIndex simValue blogId blogTitle
same-blog 1 0.98117566 392 high scalability-2008-09-24-Building a Scalable Architecture for Web Apps
Introduction: By Bhavin Turakhia CEO, Directi. Covers: * Why scalability is important. Viral marketing can result in instant success. With RSS/Ajax/SOA number of requests grow exponentially with user base. Goal is to build a web 2.0 app that can server millions of users with zero downtime. * Introduction to the variables. Scalability, performance, responsiveness, availability, downtime impact, cost, maintenance effort. * Introduction to the factors. Platform selection, hardware, application design, database architecture, deployment architecture, storage architecture, abuse prevention, monitoring mechanisms, etc. * Building our own scalable architecture in incremental steps: vertical scaling, vertical partitioning, horizontal scaling, horizontal partitioning, etc. First buy bigger. Then deploy each service on a separate node. Then increase the number of nudes and load balance. Deal with session management. Remove single points of failure. Use a shared nothing cluster. Choice of master-slave m
2 0.81066728 637 high scalability-2009-06-24-Habits of Highly Scalable Web Applications
Introduction: Nick Belhomme wrote up a excellent summary of a talk given by Eli White on building scalable web applications. Eli worked at digg.com and is now the PHP Community Manager & DevZone Editor-in-Chief at Zend Technologies. Eli takes us on a grand tour through various proven scaling strategies. On the trip you'll visit: What is scalable application design Tip 1: load balancing the webserver Tip 2: scaling from a single DB server to a Master-Slave setup Tip 3: Partitioning, Vertical DB Scaling Tip 4: Partitioning, horizontal DB Scaling Tip 5: Application Level Partitioning Tip 6: Caching to get around your database Resources
3 0.71767616 6 high scalability-2007-07-11-Friendster Architecture
Introduction: Friendster is one of the largest social network sites on the web. it emphasizes genuine friendships and the discovery of new people through friends. Site: http://www.friendster.com/ Information Sources Friendster - Scaling for 1 Billion Queries per day Platform MySQL Perl PHP Linux Apache What's Inside? Dual x86-64 AMD Opterons with 8 GB of RAM Faster disk (SAN) Optimized indexes Traditional 3-tier architecture with hardware load balancer in front of the databases Clusters based on types: ad, app, photo, monitoring, DNS, gallery search DB, profile DB, user infor DB, IM status cache, message DB, testimonial DB, friend DB, graph servers, gallery search, object cache. Lessons Learned No persistent database connections. Removed all sorts. Optimized indexes Don’t go after the biggest problems first Optimize without downtime Split load Moved sorting query types into the application and added LIMITS. Reduced ranges R
4 0.70955306 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.70574969 389 high scalability-2008-09-23-How to Scale with Ruby on Rails
Introduction: By George Palmer of 3dogsbark.com. Covers: * How you start out: shared hosting, web server DB on same machine. Move two 2 machines. Minimal code changes. * Scaling the database. Add read slaves on their own machines. Then master-master setup. Still minimal code changes. * Scaling the web server. Load balance against multiple application servers. Application servers scale but the database doesn't. * User clusters. Partition and allocate users to their own dedicated cluster. Requires substantial code changes. * Caching. A large percentage of hits are read only. Use reverse proxy, memcached, and language specific cache. * Elastic architectures. Based on Amazon EC2. Start and stop instances on demand. For global applications keep a cache on each continent, assign users to clusters by location, maintain app servers on each continent, use transaction replication software if you must replicate your site globally.
6 0.68196905 684 high scalability-2009-08-18-Real World Web: Performance & Scalability
7 0.6716792 903 high scalability-2010-09-17-Hot Scalability Links For Sep 17, 2010
8 0.66478705 157 high scalability-2007-11-16-Product: lbpool - Load Balancing JDBC Pool
9 0.66288912 391 high scalability-2008-09-23-The 7 Stages of Scaling Web Apps
10 0.66059512 1047 high scalability-2011-05-25-Stuff to Watch from Surge 2010
11 0.65544957 331 high scalability-2008-05-27-eBay Architecture
12 0.65458864 381 high scalability-2008-09-08-Guerrilla Capacity Planning and the Law of Universal Scalability
13 0.65369773 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
14 0.64273947 313 high scalability-2008-05-02-Friends for Sale Architecture - A 300 Million Page View-Month Facebook RoR App
15 0.63992482 142 high scalability-2007-11-05-Strategy: Diagonal Scaling - Don't Forget to Scale Out AND Up
16 0.63925546 182 high scalability-2007-12-12-Oracle Can Do Read-Write Splitting Too
17 0.63067901 602 high scalability-2009-05-17-Scaling Django Web Apps by Mike Malone
18 0.62322223 595 high scalability-2009-05-08-Publish-subscribe model does not scale?
19 0.62144029 873 high scalability-2010-08-06-Hot Scalability Links for Aug 6, 2010
20 0.61942297 99 high scalability-2007-09-23-HA for switches
topicId topicWeight
[(1, 0.131), (2, 0.32), (61, 0.125), (79, 0.13), (85, 0.025), (89, 0.126), (94, 0.043)]
simIndex simValue blogId blogTitle
same-blog 1 0.96582478 392 high scalability-2008-09-24-Building a Scalable Architecture for Web Apps
Introduction: By Bhavin Turakhia CEO, Directi. Covers: * Why scalability is important. Viral marketing can result in instant success. With RSS/Ajax/SOA number of requests grow exponentially with user base. Goal is to build a web 2.0 app that can server millions of users with zero downtime. * Introduction to the variables. Scalability, performance, responsiveness, availability, downtime impact, cost, maintenance effort. * Introduction to the factors. Platform selection, hardware, application design, database architecture, deployment architecture, storage architecture, abuse prevention, monitoring mechanisms, etc. * Building our own scalable architecture in incremental steps: vertical scaling, vertical partitioning, horizontal scaling, horizontal partitioning, etc. First buy bigger. Then deploy each service on a separate node. Then increase the number of nudes and load balance. Deal with session management. Remove single points of failure. Use a shared nothing cluster. Choice of master-slave m
2 0.96482611 240 high scalability-2008-02-05-Handling of Session for a site running from more than 1 data center
Introduction: If using a DB to store session(used by some app server, ex.. websphere), how would an enterprise class site that is housed in 2 different data centers(that are live/live) maintain the session between both data centers. The problem as I see it is that since each data center has their own session database, if I was to flip the users to only access Data Center 1(by changing the DNS records for the site or some other Load balancing technique) then that would cause all previous Data Center 2 users to lose their session. What would be some pure hardware based solutions to this that are being used now? That way the applications supporting the web site can be abstracted from this. As I see now, a solution is to possibly have the session databases in both centers some how replicate the data to each other. I just don't see the best way to even accomplish this you are not even guraunteed that the session ID's will be unique since it's 2 different Application Server tiers(again websphere)
3 0.96029127 1503 high scalability-2013-08-19-What can the Amazing Race to the South Pole Teach us About Startups?
Introduction: At the heart of every software adventure exists a journey in service of a quest. Melodramatic much? Sorry, but while wandering dazzled through Race to the End of the Earth , a fantastic exhibit at the Royal BC Museum on the 1911-1912 race to the South Pole between Norwegian explorer Roald Amundsen and British naval officer Robert Scott , I couldn’t help but think of the two radically different approaches each team took to the race and it shocked me to see that some of the same principles that lead to success or failure in software development also seem to lead to success or failure in exploration. I wish I could reproduce the experience of walking through the exhibit . Plaque after plaque I remember wondering out loud at Scott’s choices and then nod in agreement with Amundsen’s approach. The core conflict was straight out of any ancient Agile (Amundsen) vs Waterfall (Scott) thread you can find on Usenet. And Waterfall lost. As background here are some sources you may want
4 0.95589525 1210 high scalability-2012-03-16-Stuff The Internet Says On Scalability For March 16, 2012
Introduction: HighScalability is What We Do: 454,400 : Number of Amazon servers; 45PB : Facebook Data Warehouse, grows exponentially; 5 Atoms : Ultimate limit of thermodynamics; YouTube : 4 billion views/day, 60 hours of video uploaded every minute, revenue doubled in 2010 Quotable quotes: @adrianco : Walmart labs run large single region Cassandra clusters with Intel SSDs and have been in production for two years. Working well for them. @mybellemac : Scalability is a mother. #pinterest @fakesigi : Thanks for the correction. I saw cloud computing, scalability and my brain turned off. @BVA100 : I disagree with "If it ain't broke, don't fix it". We ought to be forward thinkers, concerned with leading indicators and scalability. Dilbert on the meaning of it all . Cassandra and Solid State Drives . DataStax's Rick Branson with a sweet explanation of how Cassandra was built for a world of spinning disks, which means it only writes sequentially, w
5 0.95488673 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
6 0.94769591 1187 high scalability-2012-02-03-Stuff The Internet Says On Scalability For February 3, 2012
7 0.94665462 160 high scalability-2007-11-19-Tailrank Architecture - Learn How to Track Memes Across the Entire Blogosphere
8 0.94488949 628 high scalability-2009-06-13-Neo4j - a Graph Database that Kicks Buttox
10 0.94286245 589 high scalability-2009-05-05-Drop ACID and Think About Data
11 0.94177544 658 high scalability-2009-07-17-Against all the odds
12 0.94153214 1509 high scalability-2013-08-30-Stuff The Internet Says On Scalability For August 30, 2013
13 0.94148797 684 high scalability-2009-08-18-Real World Web: Performance & Scalability
14 0.94136739 920 high scalability-2010-10-15-Troubles with Sharding - What can we learn from the Foursquare Incident?
15 0.94096047 993 high scalability-2011-02-22-Is Node.js Becoming a Part of the Stack? SimpleGeo Says Yes.
16 0.94087797 512 high scalability-2009-02-14-Scaling Digg and Other Web Applications
17 0.94070643 933 high scalability-2010-11-01-Hot Trend: Move Behavior to Data for a New Interactive Application Architecture
18 0.94038522 1065 high scalability-2011-06-21-Running TPC-C on MySQL-RDS
19 0.9400925 358 high scalability-2008-07-26-Sharding the Hibernate Way
20 0.93962854 1313 high scalability-2012-08-28-Making Hadoop Run Faster