high_scalability high_scalability-2008 high_scalability-2008-372 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Hi, we've got a web application, which runs without the common standalone application servers like tomcat or jboss, rather it runs with an embedded jetty server. Now we are planing to run instances of this application on multiple machines, with a load balancer serving the requests. The big question is: is there a common scenario on how to update these applications? Lets think of 10 instances on 10 machines (one instance per machine), where we want to update each of these applications version. The brute force approach would be, to stop all instances, update and then restart it. This is a lot of manual work ;) Another problem is down-time: so someone must only shutdown one server after another, but then there are multiple application versions around. Can someone please provide us with a hint for this problem? Perhaps papers, tools or something like that? Thanks a lot :)
sentIndex sentText sentNum sentScore
1 Hi, we've got a web application, which runs without the common standalone application servers like tomcat or jboss, rather it runs with an embedded jetty server. [sent-1, score-1.683]
2 Now we are planing to run instances of this application on multiple machines, with a load balancer serving the requests. [sent-2, score-0.858]
3 The big question is: is there a common scenario on how to update these applications? [sent-3, score-0.684]
4 Lets think of 10 instances on 10 machines (one instance per machine), where we want to update each of these applications version. [sent-4, score-0.961]
5 The brute force approach would be, to stop all instances, update and then restart it. [sent-5, score-0.999]
6 This is a lot of manual work ;) Another problem is down-time: so someone must only shutdown one server after another, but then there are multiple application versions around. [sent-6, score-1.261]
7 Can someone please provide us with a hint for this problem? [sent-7, score-0.643]
wordName wordTfidf (topN-words)
[('instances', 0.281), ('brute', 0.255), ('update', 0.234), ('hint', 0.234), ('standalone', 0.216), ('shutdown', 0.216), ('jetty', 0.216), ('runs', 0.191), ('someone', 0.187), ('tomcat', 0.179), ('restart', 0.173), ('application', 0.162), ('machines', 0.158), ('common', 0.152), ('papers', 0.149), ('embedded', 0.148), ('scenario', 0.148), ('force', 0.147), ('lets', 0.141), ('balancer', 0.14), ('versions', 0.139), ('thanks', 0.138), ('manual', 0.131), ('another', 0.128), ('stop', 0.121), ('jboss', 0.119), ('perhaps', 0.118), ('serving', 0.113), ('multiple', 0.111), ('problem', 0.104), ('question', 0.099), ('applications', 0.098), ('got', 0.096), ('lot', 0.089), ('please', 0.089), ('instance', 0.088), ('rather', 0.082), ('tools', 0.076), ('provide', 0.073), ('machine', 0.07), ('approach', 0.069), ('must', 0.069), ('us', 0.06), ('something', 0.058), ('one', 0.053), ('think', 0.052), ('big', 0.051), ('run', 0.051), ('per', 0.05), ('like', 0.05)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 372 high scalability-2008-08-27-Updating distributed web applications
Introduction: Hi, we've got a web application, which runs without the common standalone application servers like tomcat or jboss, rather it runs with an embedded jetty server. Now we are planing to run instances of this application on multiple machines, with a load balancer serving the requests. The big question is: is there a common scenario on how to update these applications? Lets think of 10 instances on 10 machines (one instance per machine), where we want to update each of these applications version. The brute force approach would be, to stop all instances, update and then restart it. This is a lot of manual work ;) Another problem is down-time: so someone must only shutdown one server after another, but then there are multiple application versions around. Can someone please provide us with a hint for this problem? Perhaps papers, tools or something like that? Thanks a lot :)
2 0.16843034 1331 high scalability-2012-10-02-An Epic TripAdvisor Update: Why Not Run on the Cloud? The Grand Experiment.
Introduction: This is a guest post by Shawn Hsiao , Luke Massa , and Victor Luu . Shawn runs TripAdvisor ’s Technical Operations team, Luke and Victor interned on his team this past summer. This post is introduced by Andy Gelfond , TripAdvisor’s head of engineering. It's been a little over a year since our last post about the TripAdvisor architecture . It has been an exciting year. Our business and team continues to grow, we are now an independent public company, and we have continued to keep/scale our development process and culture as we have grown - we still run dozens of independent teams, and each team continues to work across the entire stack. All that has changed are the numbers: 56M visitors per month 350M+ pages requests a day 120TB+ of warehouse data running on a large Hadoop cluster, and quickly growing We also had a very successful college intern program that brought on over 60 interns this past summer, all who were quickly on boarded and doing the same kind of work a
3 0.16010889 1286 high scalability-2012-07-18-Strategy: Kill Off Multi-tenant Instances with High CPU Stolen Time
Introduction: Are all instances created equal? Perhaps because under multi-tenancy multiple virtual machines run on the same physical host, not all applications will run equally well on every instance. In that case it makes sense to measure and move to a better performing instance. That's the interesting idea from @botchagalupe : Imagine something like a "performance monkey" where an infrastructure is so bound that it can kill lower performing instances automatically. @adrianco says Netflix has throught of doing the same: We've looked at killing off multi-tenant instances that have high CPU stolen time... Related Articles Host server CPU utilization in Amazon EC2 cloud
4 0.14923057 812 high scalability-2010-04-19-Strategy: Order Two Mediums Instead of Two Smalls and the EC2 Buffet
Introduction: Vaibhav Puranik in Web serving in the cloud – our experiences with nginx and instance sizes describes their experience trying to maximum traffic and minimum their web serving costs on EC2. Initially they tested with two m1.small instance types and then they the switched to two c1.mediums instance types. The m1s are the standard instance types and the c1s are the high CPU instance types. Obviously the mediums have greater capability, but the cost difference was interesting: In the long term they will save money using the larger instances and not autoscaling. With the small instances, traffic bursts caused autoscaling to kick in. New instances were started in response to load. The instances woud be up for a short period of time and then spin down again. This constant churn costs a lot of money. Selecting the larger instance sizes, which are capable of handling the load without autoscaling, turn out to save money even though they are more expensive. Starting new instances also tak
5 0.13800126 1371 high scalability-2012-12-12-Pinterest Cut Costs from $54 to $20 Per Hour by Automatically Shutting Down Systems
Introduction: We've long known one of the virtues of the cloud is, through the magic of services and automation, that systems can be shut or tuned down when not in use. What may be surprising is how much money can be saved. This aspect of cloudiness got a lot of pub at AWS re:Invent and is being rebranded under the term Cost-Aware Architecture . An interesting example was given by Ryan Park, Pinterest’s technical operations lead: 20% of their systems are shutdown after hours in response to traffic loads Reserved instances are used for standard traffic On-demand and spot instances are used to handle the elastic load throughout the day. When more servers are needed for an auto-scaled service, spot requests are opened and on-demand instances are started at the same time. Most services are targeted to run at about 50% on-demand and 50% spot. Watchdog processes continually check what's running. More instances are launched when needed and terminated when not needed. If spot prices spik
6 0.12476418 262 high scalability-2008-02-26-Architecture to Allow High Availability File Upload
7 0.12297053 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
8 0.10965198 1165 high scalability-2011-12-28-Strategy: Guaranteed Availability Requires Reserving Instances in Specific Zones
9 0.10453603 808 high scalability-2010-04-12-Poppen.de Architecture
10 0.10230497 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
12 0.099397302 1058 high scalability-2011-06-13-Automation on AWS with Ruby and Puppet
13 0.098290011 111 high scalability-2007-10-04-Number of load balanced servers
14 0.096613675 138 high scalability-2007-10-30-Feedblendr Architecture - Using EC2 to Scale
15 0.094624899 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
16 0.093836851 176 high scalability-2007-12-07-Synchronizing databases in different geographic locations
18 0.093158111 195 high scalability-2007-12-28-Amazon's EC2: Pay as You Grow Could Cut Your Costs in Half
19 0.092064418 936 high scalability-2010-11-09-Facebook Uses Non-Stored Procedures to Update Social Graphs
20 0.091653243 126 high scalability-2007-10-20-Should you build your next website using 3tera's grid OS?
topicId topicWeight
[(0, 0.163), (1, 0.039), (2, -0.018), (3, -0.058), (4, -0.041), (5, -0.058), (6, 0.061), (7, -0.072), (8, -0.015), (9, -0.08), (10, -0.007), (11, 0.012), (12, 0.022), (13, -0.078), (14, 0.004), (15, -0.05), (16, -0.021), (17, 0.02), (18, 0.025), (19, 0.048), (20, -0.03), (21, 0.009), (22, 0.011), (23, -0.064), (24, 0.044), (25, 0.003), (26, 0.009), (27, -0.03), (28, -0.01), (29, 0.001), (30, 0.022), (31, 0.019), (32, -0.007), (33, 0.087), (34, -0.068), (35, -0.046), (36, -0.032), (37, -0.138), (38, 0.046), (39, 0.02), (40, -0.027), (41, 0.04), (42, -0.039), (43, -0.005), (44, -0.049), (45, -0.038), (46, 0.014), (47, 0.017), (48, -0.034), (49, 0.012)]
simIndex simValue blogId blogTitle
same-blog 1 0.95659596 372 high scalability-2008-08-27-Updating distributed web applications
Introduction: Hi, we've got a web application, which runs without the common standalone application servers like tomcat or jboss, rather it runs with an embedded jetty server. Now we are planing to run instances of this application on multiple machines, with a load balancer serving the requests. The big question is: is there a common scenario on how to update these applications? Lets think of 10 instances on 10 machines (one instance per machine), where we want to update each of these applications version. The brute force approach would be, to stop all instances, update and then restart it. This is a lot of manual work ;) Another problem is down-time: so someone must only shutdown one server after another, but then there are multiple application versions around. Can someone please provide us with a hint for this problem? Perhaps papers, tools or something like that? Thanks a lot :)
2 0.7999531 1331 high scalability-2012-10-02-An Epic TripAdvisor Update: Why Not Run on the Cloud? The Grand Experiment.
Introduction: This is a guest post by Shawn Hsiao , Luke Massa , and Victor Luu . Shawn runs TripAdvisor ’s Technical Operations team, Luke and Victor interned on his team this past summer. This post is introduced by Andy Gelfond , TripAdvisor’s head of engineering. It's been a little over a year since our last post about the TripAdvisor architecture . It has been an exciting year. Our business and team continues to grow, we are now an independent public company, and we have continued to keep/scale our development process and culture as we have grown - we still run dozens of independent teams, and each team continues to work across the entire stack. All that has changed are the numbers: 56M visitors per month 350M+ pages requests a day 120TB+ of warehouse data running on a large Hadoop cluster, and quickly growing We also had a very successful college intern program that brought on over 60 interns this past summer, all who were quickly on boarded and doing the same kind of work a
3 0.75551081 812 high scalability-2010-04-19-Strategy: Order Two Mediums Instead of Two Smalls and the EC2 Buffet
Introduction: Vaibhav Puranik in Web serving in the cloud – our experiences with nginx and instance sizes describes their experience trying to maximum traffic and minimum their web serving costs on EC2. Initially they tested with two m1.small instance types and then they the switched to two c1.mediums instance types. The m1s are the standard instance types and the c1s are the high CPU instance types. Obviously the mediums have greater capability, but the cost difference was interesting: In the long term they will save money using the larger instances and not autoscaling. With the small instances, traffic bursts caused autoscaling to kick in. New instances were started in response to load. The instances woud be up for a short period of time and then spin down again. This constant churn costs a lot of money. Selecting the larger instance sizes, which are capable of handling the load without autoscaling, turn out to save money even though they are more expensive. Starting new instances also tak
4 0.74315381 1058 high scalability-2011-06-13-Automation on AWS with Ruby and Puppet
Introduction: This is a guest post by Frédéric Faure (architect at Ysance ), you can follow him on twitter . Urbandive is an immersive view service launched by the French YellowPages which allows you to travel in cities in France thanks to a 360° view. Urbandive focuses on providing high definition pictures and accurate professional and social content. One of the biggest jobs was to enable a fast scalable architecture, because it was really difficult to forecast the traffic load at production time. Traffic load may be influenced if the service receives attention from users as a result of advertising. Below you will find a summary of the goals we achieve by using a Ruby scheduler built on top of Puppet on AWS to create a complete infrastructure. Workflow & XTR-Lucid Our scalability combo is : a home-made Ruby scheduler ( XTR-Lucid ) to deal with AWS APIs + the Puppet Master to install services and configure EC2 instances and keep them up-to-date during all the product
5 0.73648649 1165 high scalability-2011-12-28-Strategy: Guaranteed Availability Requires Reserving Instances in Specific Zones
Introduction: When EC2 first started the mental model was of a magic Pez dispenser supplying an infinite stream of instances in any desired flavor. If you needed an instance, because of a either a failure or traffic spike, it would be there. As amazing as EC2 is, this model turned out to be optimistic. From a thread on the Amazon discussion forum we learn any dispenser has limits: As Availability Zones grow over time, our ability to continue to expand them can become constrained. In these scenarios, we will prevent customers from launching in the constrained zone if they do not yet have existing resources in that zone. We also might remove the constrained zone entirely from the list of options for new customers. This means that occasionally, different customers will see a different number of Availability Zones in a particular Region. Both approaches aim to help customers avoid accidentally starting to build up their infrastructure in an Availability Zone where they might have less ability
6 0.73485166 1371 high scalability-2012-12-12-Pinterest Cut Costs from $54 to $20 Per Hour by Automatically Shutting Down Systems
7 0.71235454 1286 high scalability-2012-07-18-Strategy: Kill Off Multi-tenant Instances with High CPU Stolen Time
9 0.68179697 1260 high scalability-2012-06-07-Case Study on Scaling PaaS infrastructure
10 0.67767441 1023 high scalability-2011-04-14-Strategy: Cache Application Start State to Reduce Spin-up Times
11 0.67229557 1248 high scalability-2012-05-21-Pinterest Architecture Update - 18 Million Visitors, 10x Growth,12 Employees, 410 TB of Data
12 0.67186588 1353 high scalability-2012-11-01-Cost Analysis: TripAdvisor and Pinterest costs on the AWS cloud
13 0.6706453 138 high scalability-2007-10-30-Feedblendr Architecture - Using EC2 to Scale
14 0.66903126 1543 high scalability-2013-11-05-10 Things You Should Know About AWS
15 0.64480454 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
16 0.63812286 1347 high scalability-2012-10-25-Not All Regions are Created Equal - South America Es Bueno
17 0.62963575 881 high scalability-2010-08-16-Scaling an AWS infrastructure - Tools and Patterns
18 0.61683249 798 high scalability-2010-03-22-7 Secrets to Successfully Scaling with Scalr (on Amazon) by Sebastian Stadil
19 0.61671484 1126 high scalability-2011-09-27-Use Instance Caches to Save Money: Latency == $$$
topicId topicWeight
[(1, 0.087), (2, 0.038), (79, 0.749)]
simIndex simValue blogId blogTitle
1 0.99949664 743 high scalability-2009-11-23-Big Data on Grids or on Clouds?
Introduction: Contributed by Wolfgang Gentzsch: Now that we have a new computing paradigm, Cloud Computing, how can Clouds help our data? Replace our internal data vaults as we hoped Grids would? Are Grids dead now that we have Clouds? Despite all the promising developments in the Grid and Cloud computing space, and the avalanche of publications and talks on this subject, many people still seem to be confused about internal data and compute resources, versus Grids versus Clouds, and they are hesitant to take the next step. I think there are a number of issues driving this uncertainty. read more at: BigDataMatters.com
2 0.99831247 8 high scalability-2007-07-12-Should I use LAMP or Windows?
Introduction: Hi, I stumb l ed on your s i te and I am th i nking about start i ng a website. I haven't rece i ved a good answer about what I shou l d use to bui l d i t, so I thought I wou l d give it a shot. I am a w i ndows guy. I know .Net and ASP and how to bu i ld web s i tes using that stack. But I not i ce most sites use LAMP and that's what most people ta l k about using. What's wrong w i th using Windows? .Net Programmer
3 0.99186373 692 high scalability-2009-09-01-Cheap storage: how backblaze takes matters in hand
Introduction: Blackblaze blogs about how they built their own storage infrastructure on the cheap to run their cloud backup service. This episode: the hardware. Sorry, just a link this time.
4 0.99186373 1119 high scalability-2011-09-20-HighScalability is old news. Step your scaling game way up... (NSFW cartoon)
Introduction: Jeremy Raines tweeted a link to this cartoon my new filing technique is unstoppable , showing how scotch tape can be used to create a new super-database. Very funny in a Dilbert sort of way, but definitely not NSFW... For more on Twisted Tuesday, you may enjoy: Hilarious Video: Relational Database Vs NoSQL Fanbois NSFW: Hilarious Fault-Tolerance Cartoon
5 0.98702222 782 high scalability-2010-02-23-When to migrate your database?
Introduction: Why migrate your database? Efficiency and availability problems are harming your business – reports are out of date, your batch processing window is nearing its limits, outages (unplanned/planned) frequently halt work. Database consolidation – remove the costs that result from a heterogeneous database environment (DBAs time, database vendor pricing, database versions, hardware, OSs, patches, upgrades etc.). OK, so the driving forces for migration are clear, what now? Read more on BigDataMatters.com
6 0.98684871 443 high scalability-2008-11-14-Paper: Pig Latin: A Not-So-Foreign Language for Data Processing
same-blog 7 0.98454356 372 high scalability-2008-08-27-Updating distributed web applications
8 0.97115463 107 high scalability-2007-10-02-Some Real Financial Numbers for Your Startup
9 0.96802324 401 high scalability-2008-10-04-Is MapReduce going mainstream?
10 0.96467435 1100 high scalability-2011-08-18-Paper: The Akamai Network - 61,000 servers, 1,000 networks, 70 countries
11 0.94661021 1277 high scalability-2012-07-05-10 Golden Principles For Building Successful Mobile-Web Applications
12 0.93975431 1169 high scalability-2012-01-05-Shutterfly Saw a Speedup of 500% With Flashcache
13 0.92198104 784 high scalability-2010-02-25-Paper: High Performance Scalable Data Stores
14 0.91962361 323 high scalability-2008-05-19-Twitter as a scalability case study
15 0.87350023 75 high scalability-2007-08-28-Google Utilities : An online google guide,tools and Utilities.
16 0.86789709 871 high scalability-2010-08-04-Dremel: Interactive Analysis of Web-Scale Datasets - Data as a Programming Paradigm
17 0.86618471 1162 high scalability-2011-12-23-Funny: A Cautionary Tale About Storage and Backup
18 0.83999813 680 high scalability-2009-08-13-Reconnoiter - Large-Scale Trending and Fault-Detection
19 0.83713055 1403 high scalability-2013-02-08-Stuff The Internet Says On Scalability For February 8, 2013
20 0.83178735 650 high scalability-2009-07-02-Product: Hbase