high_scalability high_scalability-2013 high_scalability-2013-1387 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Colin Scott , a Berkeley researcher, updated Jeff Dean’s famous Numbers Everyone Should Know with his Latency Numbers Every Programmer Should Know interactive graphic. The interactive aspect is cool because it has a slider that let’s you see numbers back from as early as 1990 to the far far future of 2020. Colin explained his motivation for updating the numbers : The other day, a friend mentioned a latency number to me, and I realized that it was an order of magnitude smaller than what I had memorized from Jeff’s talk. The problem, of course, is that hardware performance increases exponentially! After some digging, I actually found that the numbers Jeff quotes are over a decade old Since numbers without interpretation are simply data, take a look at Google Pro Tip: Use Back-Of-The-Envelope-Calculations To Choose The Best Design . The idea is back-of-the-envelope calculations are estimates you create using a combination of thought experiments and common perfor
sentIndex sentText sentNum sentScore
1 The interactive aspect is cool because it has a slider that let’s you see numbers back from as early as 1990 to the far far future of 2020. [sent-2, score-0.548]
2 Colin explained his motivation for updating the numbers : The other day, a friend mentioned a latency number to me, and I realized that it was an order of magnitude smaller than what I had memorized from Jeff’s talk. [sent-3, score-0.684]
3 After some digging, I actually found that the numbers Jeff quotes are over a decade old Since numbers without interpretation are simply data, take a look at Google Pro Tip: Use Back-Of-The-Envelope-Calculations To Choose The Best Design . [sent-5, score-0.636]
4 The idea is back-of-the-envelope calculations are estimates you create using a combination of thought experiments and common performance numbers to a get a good feel for which designs will meet your requirements. [sent-6, score-0.351]
5 dmazzoni : Yeah, but the latency numbers help a lot in interpreting profiling results. [sent-12, score-0.589]
6 that to do anything practical with these latency numbers, you also need to know the parallelism of your processor and the parallelizability of your access patterns. [sent-15, score-0.309]
7 the pure latency number only matters if you are limited to one access at a time. [sent-16, score-0.309]
8 Particularly misleading is that it has numbers for SSDs in 1991. [sent-19, score-0.407]
9 , make branching predictable; or make it branch free if possible); prefer L1 cache to L2, (to L3) to main memory to SSD to HDD to pulled from faraway network; prefer sequential reads to random reads; especially from an HDD. [sent-25, score-0.56]
10 , why does this array patrickwiseman : With timings that are several orders of magnitude in difference I'd just ignore the constants between factors as they change too frequently. [sent-30, score-0.414]
11 Also there is a difference between latency and bandwidth and the chart is simply inconsistent. [sent-31, score-0.297]
12 CPU Cache Hit ~ 10 time units Something that was located close to something else that was just accessed by either time or location. [sent-34, score-0.511]
13 Memory Access ~ 100 time units Something that most likely has been accessed recently, but not immediately previously in the code. [sent-35, score-0.344]
14 Disk Access ~ 1,000,000 time units It's been paged out to disk because it's accessed too infrequently or is too big to fit in memory. [sent-36, score-0.344]
15 HoLyVieR : The idea is more about knowing the scale of time it takes to help compare different solution. [sent-41, score-0.272]
16 cojoco : And as latency goes up, it makes more sense to optimise for cache use, and you can make some huge speed-ups by reordering memory accesses appropriately. [sent-55, score-0.619]
17 Obviously, you only have 1 display latency in your pipeline but it's still typically the biggest single latency. [sent-60, score-0.34]
18 It's a little over 5000 miles from CA to the Netherlands, so light takes about 30ms to travel that far on a vacuum. [sent-62, score-0.323]
19 According to Agner, a TEST involving cache takes 1 cycle (1/2. [sent-69, score-0.33]
20 53 ns on my system), and a CMOVZ takes a variable amount of time (by their numbers, this should take roughly 12 cycles (1 to test the zflag, 11 to write to L2 cache). [sent-70, score-0.483]
wordName wordTfidf (topN-words)
[('numbers', 0.285), ('latency', 0.231), ('ns', 0.205), ('magnitude', 0.168), ('units', 0.165), ('mutex', 0.153), ('cache', 0.133), ('takes', 0.125), ('nanosecond', 0.122), ('colin', 0.122), ('misleading', 0.122), ('nanoseconds', 0.113), ('jeff', 0.111), ('display', 0.109), ('orders', 0.105), ('light', 0.103), ('memory', 0.099), ('accessed', 0.098), ('branch', 0.097), ('far', 0.095), ('fiber', 0.093), ('accesses', 0.088), ('netherlands', 0.087), ('something', 0.086), ('trip', 0.082), ('time', 0.081), ('prefer', 0.079), ('access', 0.078), ('threadson', 0.073), ('interpreting', 0.073), ('thankful', 0.073), ('zettabyte', 0.073), ('slider', 0.073), ('relativity', 0.073), ('amazes', 0.073), ('lcd', 0.073), ('faraway', 0.073), ('constants', 0.073), ('round', 0.073), ('roughly', 0.072), ('cycle', 0.072), ('faster', 0.07), ('reordering', 0.068), ('yottabyte', 0.068), ('meijer', 0.068), ('guessing', 0.068), ('timings', 0.068), ('idea', 0.066), ('simply', 0.066), ('particularly', 0.066)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000002 1387 high scalability-2013-01-15-More Numbers Every Awesome Programmer Must Know
Introduction: Colin Scott , a Berkeley researcher, updated Jeff Dean’s famous Numbers Everyone Should Know with his Latency Numbers Every Programmer Should Know interactive graphic. The interactive aspect is cool because it has a slider that let’s you see numbers back from as early as 1990 to the far far future of 2020. Colin explained his motivation for updating the numbers : The other day, a friend mentioned a latency number to me, and I realized that it was an order of magnitude smaller than what I had memorized from Jeff’s talk. The problem, of course, is that hardware performance increases exponentially! After some digging, I actually found that the numbers Jeff quotes are over a decade old Since numbers without interpretation are simply data, take a look at Google Pro Tip: Use Back-Of-The-Envelope-Calculations To Choose The Best Design . The idea is back-of-the-envelope calculations are estimates you create using a combination of thought experiments and common perfor
2 0.2477233 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
Introduction: Update 8 : The Cost of Latency by James Hamilton. James summarizing some latency info from Steve Souder , Greg Linden , and Marissa Mayer . Speed [is] an undervalued and under-discussed asset on the web. Update 7: How do you know when you need more memcache servers? . Dathan Pattishall talks about using memcache not to scale, but to reduce latency and reduce I/O spikes, and how to use stats to know when more servers are needed. Update 6: Stock Traders Find Speed Pays, in Milliseconds . Goldman Sachs is making record profits off a 500 millisecond trading advantage. Yes, latency matters. As an interesting aside, Libet found 500 msecs is about the time it takes the brain to weave together an experience of consciousness from all our sensor inputs. Update 5: Shopzilla's Site Redo - You Get What You Measure . At the Velocity conference Phil Dixon, from Shopzilla, presented data showing a 5 second speed up resulted in a 25% increase in page views, a 10% increas
3 0.18032931 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results
Introduction: Likewise the current belief that, in the case of artificial machines the very large and the very small are equally feasible and lasting is a manifest error. Thus, for example, a small obelisk or column or other solid figure can certainly be laid down or set up without danger of breaking, while the large ones will go to pieces under the slightest provocation, and that purely on account of their own weight. -- Galileo Galileo observed how things broke if they were naively scaled up. Interestingly, Google noticed a similar pattern when building larger software systems using the same techniques used to build smaller systems. Luiz André Barroso , Distinguished Engineer at Google, talks about this fundamental property of scaling systems in his fascinating talk, Warehouse-Scale Computing: Entering the Teenage Decade . Google found the larger the scale the greater the impact of latency variability. When a request is implemented by work done in parallel, as is common with today's service
4 0.16792795 978 high scalability-2011-01-26-Google Pro Tip: Use Back-of-the-envelope-calculations to Choose the Best Design
Introduction: How do you know which is the "best" design for a given problem? If, for example, you were given the problem of generating an image search results page of 30 thumbnails, would you load images sequentially? In parallel? Would you cache? How would you decide? If you could harness the power of the multiverse you could try every possible option in the design space and see which worked best. But that's crazy impractical, isn't it? Another option is to consider the order of various algorithm alternatives. As a prophet for the Golden Age of Computational Thinking , Google would definitely do this, but what else might Google do? Use Back-of-the-envelope Calculations to Evaluate Different Designs Jeff Dean , Head of Google's School of Infrastructure Wizardry—instrumental in many of Google's key systems: ad serving, BigTable; search, MapReduce, ProtocolBuffers—advocates evaluating different designs using back-of-the-envelope calculations . He gives the full story in this Stanfor
5 0.16223429 1202 high scalability-2012-03-01-Grace Hopper to Programmers: Mind Your Nanoseconds!
Introduction: Computing pioneer Grace Hopper , inventor of the compiler , searched for a concrete way to create an intuitive understanding of just how fast is a nanosecond, a billionth of a second, which was the speed of their new computer circuits. As an illustration she settled on the length of wire that is as long as light can travel in one nanosecond. The length is a very portable 11.8 inches . A microseconds worth of wire is a still portable, but a much bulkier 984 feet. In one millisecond light travels 186 miles, which only Hercules could carry. In today's terms, at a 3.06 GHz clock speed , there's .33 nanoseconds between ticks, or 3.73 inches of light travel. Understanding the profligate ways of programmers, she suggests that every programmer wear a necklace of a microseconds worth of wire so they know what they are wasting when they throw away microseconds. And if a General is busting your chops about satellite messages taking too long to send, you can bust out your piece of wire and e
6 0.15747169 1560 high scalability-2013-12-09-In Memory: Grace Hopper to Programmers: Mind Your Nanoseconds!
7 0.15111966 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
10 0.13858074 1291 high scalability-2012-07-25-Vertical Scaling Ascendant - How are SSDs Changing Architectures?
11 0.1318846 1475 high scalability-2013-06-13-Busting 4 Modern Hardware Myths - Are Memory, HDDs, and SSDs Really Random Access?
12 0.12653489 1413 high scalability-2013-02-27-42 Monster Problems that Attack as Loads Increase
13 0.1226592 360 high scalability-2008-08-04-A Bunch of Great Strategies for Using Memcached and MySQL Better Together
14 0.12066422 721 high scalability-2009-10-13-Why are Facebook, Digg, and Twitter so hard to scale?
15 0.11691704 920 high scalability-2010-10-15-Troubles with Sharding - What can we learn from the Foursquare Incident?
16 0.11574349 1564 high scalability-2013-12-13-Stuff The Internet Says On Scalability For December 13th, 2013
17 0.11480263 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability
18 0.11220222 120 high scalability-2007-10-11-How Flickr Handles Moving You to Another Shard
19 0.11186429 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
topicId topicWeight
[(0, 0.217), (1, 0.147), (2, -0.027), (3, -0.002), (4, -0.055), (5, 0.027), (6, 0.018), (7, 0.141), (8, -0.066), (9, -0.06), (10, -0.019), (11, -0.078), (12, -0.004), (13, 0.09), (14, -0.007), (15, -0.025), (16, -0.006), (17, 0.009), (18, -0.022), (19, -0.01), (20, -0.017), (21, 0.022), (22, 0.07), (23, 0.053), (24, -0.008), (25, 0.009), (26, -0.023), (27, -0.019), (28, -0.038), (29, -0.015), (30, 0.011), (31, 0.018), (32, 0.027), (33, 0.021), (34, -0.039), (35, 0.082), (36, 0.044), (37, 0.039), (38, 0.028), (39, -0.01), (40, -0.003), (41, 0.047), (42, 0.028), (43, -0.036), (44, 0.008), (45, -0.042), (46, 0.038), (47, -0.009), (48, 0.022), (49, -0.019)]
simIndex simValue blogId blogTitle
same-blog 1 0.98488063 1387 high scalability-2013-01-15-More Numbers Every Awesome Programmer Must Know
Introduction: Colin Scott , a Berkeley researcher, updated Jeff Dean’s famous Numbers Everyone Should Know with his Latency Numbers Every Programmer Should Know interactive graphic. The interactive aspect is cool because it has a slider that let’s you see numbers back from as early as 1990 to the far far future of 2020. Colin explained his motivation for updating the numbers : The other day, a friend mentioned a latency number to me, and I realized that it was an order of magnitude smaller than what I had memorized from Jeff’s talk. The problem, of course, is that hardware performance increases exponentially! After some digging, I actually found that the numbers Jeff quotes are over a decade old Since numbers without interpretation are simply data, take a look at Google Pro Tip: Use Back-Of-The-Envelope-Calculations To Choose The Best Design . The idea is back-of-the-envelope calculations are estimates you create using a combination of thought experiments and common perfor
2 0.88113207 1475 high scalability-2013-06-13-Busting 4 Modern Hardware Myths - Are Memory, HDDs, and SSDs Really Random Access?
Introduction: "It’s all a numbers game – the dirty little secret of scalable systems" Martin Thompson is a High Performance Computing Specialist with a real mission to teach programmers how to understand the innards of modern computing systems. He has many talks and classes (listed below) on caches, buffers, memory controllers, processor architectures, cache lines, etc. His thought is programmers do not put a proper value on understanding how the underpinnings of our systems work. We gravitate to the shiny and trendy. His approach is not to teach people specific programming strategies, but to teach programmers to fish so they can feed themselves. Without a real understanding strategies are easy to apply wrongly. It's strange how programmers will put a lot of effort into understanding complicated frameworks like Hibernate, but little effort into understanding the underlying hardware on which their programs run. A major tenant of Martin's approach is to "lead by experimental observation
3 0.81140149 978 high scalability-2011-01-26-Google Pro Tip: Use Back-of-the-envelope-calculations to Choose the Best Design
Introduction: How do you know which is the "best" design for a given problem? If, for example, you were given the problem of generating an image search results page of 30 thumbnails, would you load images sequentially? In parallel? Would you cache? How would you decide? If you could harness the power of the multiverse you could try every possible option in the design space and see which worked best. But that's crazy impractical, isn't it? Another option is to consider the order of various algorithm alternatives. As a prophet for the Golden Age of Computational Thinking , Google would definitely do this, but what else might Google do? Use Back-of-the-envelope Calculations to Evaluate Different Designs Jeff Dean , Head of Google's School of Infrastructure Wizardry—instrumental in many of Google's key systems: ad serving, BigTable; search, MapReduce, ProtocolBuffers—advocates evaluating different designs using back-of-the-envelope calculations . He gives the full story in this Stanfor
4 0.80239052 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
Introduction: Update 8 : The Cost of Latency by James Hamilton. James summarizing some latency info from Steve Souder , Greg Linden , and Marissa Mayer . Speed [is] an undervalued and under-discussed asset on the web. Update 7: How do you know when you need more memcache servers? . Dathan Pattishall talks about using memcache not to scale, but to reduce latency and reduce I/O spikes, and how to use stats to know when more servers are needed. Update 6: Stock Traders Find Speed Pays, in Milliseconds . Goldman Sachs is making record profits off a 500 millisecond trading advantage. Yes, latency matters. As an interesting aside, Libet found 500 msecs is about the time it takes the brain to weave together an experience of consciousness from all our sensor inputs. Update 5: Shopzilla's Site Redo - You Get What You Measure . At the Velocity conference Phil Dixon, from Shopzilla, presented data showing a 5 second speed up resulted in a 25% increase in page views, a 10% increas
5 0.79265463 1407 high scalability-2013-02-15-Stuff The Internet Says On Scalability For February 15, 2013
Introduction: Hey, it's HighScalability time: The Herokulypse. A cautionary tale of what can happen when scalability is left for later. Rap Genius created quite a stir ( reddit , Hacker News ) when they documented high costs ($20K/month for 15 million monthly uniques) and poor performance (6 second average response times) using Heroku's random routing mesh . The cause was tracked to queuing at the dyno level when the expectation was requests are routed to free dynos. Heroku admits this is a problem . So poor load balancing combined with RoR single threading = poor performance, one that adding more dynos and spending more money won't necessarily help. While it seems clear Heroku didn't make this aspect of their system crystal clear, the incident has generated a lot of teaching moments, if you slog through it all. This is a developing story. You need money to feed the beast. Fred Wilson has some revenue ideas for you : Paid App Downloads - ex. WhatsApp; In-app purchases - ex. Zynga Poke
6 0.78918606 1462 high scalability-2013-05-22-Strategy: Stop Using Linked-Lists
7 0.78495842 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results
8 0.78091007 1588 high scalability-2014-01-31-Stuff The Internet Says On Scalability For January 31st, 2014
9 0.77251136 1246 high scalability-2012-05-16-Big List of 20 Common Bottlenecks
10 0.7575621 1652 high scalability-2014-05-21-9 Principles of High Performance Programs
11 0.75672048 1621 high scalability-2014-03-28-Stuff The Internet Says On Scalability For March 28th, 2014
12 0.75290406 1318 high scalability-2012-09-07-Stuff The Internet Says On Scalability For September 7, 2012
13 0.75071359 1237 high scalability-2012-05-02-12 Ways to Increase Throughput by 32X and Reduce Latency by 20X
14 0.74015999 1460 high scalability-2013-05-17-Stuff The Internet Says On Scalability For May 17, 2013
15 0.73822552 1592 high scalability-2014-02-07-Stuff The Internet Says On Scalability For February 7th, 2014
16 0.73443955 1471 high scalability-2013-06-06-Paper: Memory Barriers: a Hardware View for Software Hackers
17 0.73295504 823 high scalability-2010-05-05-How will memristors change everything?
18 0.73289573 1190 high scalability-2012-02-10-Stuff The Internet Says On Scalability For February 10, 2012
19 0.73211879 1369 high scalability-2012-12-10-Switch your databases to Flash storage. Now. Or you're doing it wrong.
20 0.73086137 1558 high scalability-2013-12-04-How Can Batching Requests Actually Reduce Latency?
topicId topicWeight
[(1, 0.078), (2, 0.267), (10, 0.045), (27, 0.024), (30, 0.057), (33, 0.117), (40, 0.014), (47, 0.015), (51, 0.012), (61, 0.065), (64, 0.032), (77, 0.03), (79, 0.091), (85, 0.05), (94, 0.04)]
simIndex simValue blogId blogTitle
same-blog 1 0.94161111 1387 high scalability-2013-01-15-More Numbers Every Awesome Programmer Must Know
Introduction: Colin Scott , a Berkeley researcher, updated Jeff Dean’s famous Numbers Everyone Should Know with his Latency Numbers Every Programmer Should Know interactive graphic. The interactive aspect is cool because it has a slider that let’s you see numbers back from as early as 1990 to the far far future of 2020. Colin explained his motivation for updating the numbers : The other day, a friend mentioned a latency number to me, and I realized that it was an order of magnitude smaller than what I had memorized from Jeff’s talk. The problem, of course, is that hardware performance increases exponentially! After some digging, I actually found that the numbers Jeff quotes are over a decade old Since numbers without interpretation are simply data, take a look at Google Pro Tip: Use Back-Of-The-Envelope-Calculations To Choose The Best Design . The idea is back-of-the-envelope calculations are estimates you create using a combination of thought experiments and common perfor
2 0.93431807 1315 high scalability-2012-08-30-Stuff The Internet Says On Scalability For August 31, 2012
Introduction: It's HighScalability Time: LHC compute jobs: use 1.5 CPU millennia every 3 days ; Obama helps load test Reddit: 4.3 million page views Quotable Quotes: @secastro : Want to see nearly a terabyte of memory? @DZone : Apache Projects are the Justice League of Scalability Apple And Google Might Be Negotiating Patents . Remember when empires and nation states would have a nice little summer war and then negotiate boundary lines and terms of trade? Google Faculty Summit 2012: The Online Revolution - Education at Scale . Someday we may have direct knowledge downloads and augmented wisdom packs, but until then these primitive attempts at learning process improvement are a good start. OnLive lost: how the paradise of streaming games was undone by one man's ego . The fascinating story behind a radical idea: applications hosted and rendered in the cloud while being displayed remotely on a device. You might have thought latency would be the killer
3 0.92913312 1490 high scalability-2013-07-12-Stuff The Internet Says On Scalability For July 12, 2013
Introduction: Hey, it's HighScalability time: (The Shard Scaling 6 ) 3500+ : number of species found underneath miles of ice; 360 TB/disc data capacity : 5D optical memory in glass; 50% Of Internet Traffic : Comes From Only 35 Sites/Services; 60 billion : potential alien planets that could give Snowden asylum Quotable Quotes: @ieure : "How concert app Loudie doubled its users in two weeks" The other co-founder finally signed in. @michalbe : "Daddy, how is software made?" "Well, when a programmer loves an idea very much they stay up all night and then push to github the next day" @TomDSweeney : Alan Kay: “The past 30 years have been completely mundane. It’s all been scaling (of old technology) and Angry Birds” Rick Branson : Adopt a technology by understanding what it's best at and letting it do that first, then expand… K. Eric Drexler : System-level design seeks flexible models and accepts complexity, accepts imprecision and buries i
4 0.92669022 619 high scalability-2009-06-05-HotPads Shows the True Cost of Hosting on Amazon
Introduction: Mather Corgan, president of HotPads, gave a great talk on how HotPads uses AWS to run their real estate search engine. I loved the presentation for a few reasons: It gives real costs on on their servers, how many servers they have, what they are used for, and exactly how they use S2, EBS, CloudFront and other AWS services. This is great information for anybody trying to architect a system and wondering where to run it. HotPads is a "real" application. It's a small company and at 4.5 million page-views/month it's large but not super large. It has custom server side components like indexing engines, image processing, and background database update engines for syncing new real estate data. And it also stores a lot of images and has low latency requirements. This a really good example mix of where many companies are or would like to be with their applications. Their total costs are about $11K/month, which is about what they were paying at their previous provider. I found this is
5 0.91831374 686 high scalability-2009-08-20-VMware to bridge a DMZ.
Introduction: Hey guys, There is a renewed push at my organization to deploy vmware...everywhere. I am rather excited as I know we have a lot of waste when it comes to resources. What has pricked my ears up however, is the notion of using this technology in our very busy public facing DMZ's. Today we get lots of spikes of traffic and we are coping very well. 40x HP blades, apache/php/perl/tomcat/ all in HA behind HA F5's and HA Checkpoint FW's. (20 servers in 2 datacentres). The idea is, we virtualise these machines, including the firewalls onto hosts vmware clusters that span the public interface to our internal networks. This is something that has gone against the #1 rule I have ever lived by while working on the inet. No airgaps from the unknown to the known! I am interested in feedback on this scenario. From a resource perspective, our resource requirements in the DMZ will be lowered over time due to business change and we still have a lot of head room in our capacity. Do you think t
6 0.91444224 1067 high scalability-2011-06-24-Stuff The Internet Says On Scalability For June 24, 2011
7 0.91339397 1418 high scalability-2013-03-06-Low Level Scalability Solutions - The Aggregation Collection
8 0.91326457 76 high scalability-2007-08-29-Skype Failed the Boot Scalability Test: Is P2P fundamentally flawed?
9 0.91218376 1475 high scalability-2013-06-13-Busting 4 Modern Hardware Myths - Are Memory, HDDs, and SSDs Really Random Access?
10 0.91018915 1204 high scalability-2012-03-06-Ask For Forgiveness Programming - Or How We'll Program 1000 Cores
11 0.90994775 1456 high scalability-2013-05-13-The Secret to 10 Million Concurrent Connections -The Kernel is the Problem, Not the Solution
12 0.90990633 1010 high scalability-2011-03-24-Strategy: Disk Backup for Speed, Tape Backup to Save Your Bacon, Just Ask Google
13 0.90943694 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
14 0.9092918 1421 high scalability-2013-03-11-Low Level Scalability Solutions - The Conditioning Collection
15 0.90912622 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results
16 0.90857208 1564 high scalability-2013-12-13-Stuff The Internet Says On Scalability For December 13th, 2013
17 0.90838158 1509 high scalability-2013-08-30-Stuff The Internet Says On Scalability For August 30, 2013
18 0.90820342 1602 high scalability-2014-02-26-The WhatsApp Architecture Facebook Bought For $19 Billion
19 0.90787679 1622 high scalability-2014-03-31-How WhatsApp Grew to Nearly 500 Million Users, 11,000 cores, and 70 Million Messages a Second
20 0.90702963 221 high scalability-2008-01-24-Mailinator Architecture