high_scalability high_scalability-2014 high_scalability-2014-1654 knowledge-graph by maker-knowledge-mining

1654 high scalability-2014-06-05-Cloud Architecture Revolution


meta infos for this blog

Source: html

Introduction: The introduction of cloud technologies is not a simple evolution of existing ones, but a real revolution.  Like all revolutions, it changes the points of views and redefines all the meanings. Nothing is as before.  This post wants to analyze some key words and concepts, usually used in traditional architectures, redefining them according the standpoint of the cloud.  Understanding the meaning of new words is crucial to grasp the essence of a pure cloud architecture. << There is no greater impediment to the advancement of knowledge than the ambiguity of words. >> THOMAS REID, Essays on the Intellectual Powers of Man Nowadays, it is required to challenge the limits of traditional architectures that go beyond the normal concepts of scalability and support millions of users (What's Up 500 Million) billions of transactions per day (Salesforce 1.3 billion), five 9s of availability (99.999 AOL).  I wish all of you the success of the examples cited above, but do not think that it is co


Summary: the most important sentenses genereted by tfidf model

sentIndex sentText sentNum sentScore

1 This post wants to analyze some key words and concepts, usually used in traditional architectures, redefining them according the standpoint of the cloud. [sent-4, score-0.46]

2 >> THOMAS REID, Essays on the Intellectual Powers of Man Nowadays, it is required to challenge the limits of traditional architectures that go beyond the normal concepts of scalability and support millions of users (What's Up 500 Million) billions of transactions per day (Salesforce 1. [sent-7, score-0.46]

3 Infrastructure - commodity HW instead of high-end HW This is the first shocking concept to understand about the cloud architectures. [sent-14, score-0.542]

4 The largest cloud services providers like Amazon or Azure use commodity hardware so prone to breakdowns and other problems more than the traditional environments. [sent-16, score-0.558]

5 Anyway, this kind of hardware does not prevent the use of the cloud for the enterprise applications with high availability and high-performance requirements, it is simply necessary to redesign the architecture according to different criteria of resilience and distribution. [sent-17, score-0.643]

6 Scalability - dynamic instead of static The scalability is one of the important features of a good architecture design even in the traditional approach. [sent-18, score-0.481]

7 This leads to implement very stable architectures over the time and sized for the maximum load that the application or service must support. [sent-20, score-0.527]

8 Nowadays architecture is required to adapt according to the demands and be able to expand by adding new nodes or contract. [sent-23, score-0.549]

9 Availability - resiliency instead of no failure The traditional architectures consider the resources always available. [sent-26, score-0.601]

10 In the cloud, the unavailability of a resource is no longer an exceptional event due to the use of commodity HW or because of a resource, such as an application server, is not available due to a sudden and wanted downsize. [sent-28, score-0.627]

11 In the most advanced cloud architectures, there are some agents designed to generate failures deliberately in the production environments to ensure that the application is able to respond appropriately. [sent-31, score-0.482]

12 When the worker role takes over a request, it is not completely removed even if it is no longer available for processing by other worker roles. [sent-35, score-0.717]

13 In case the processing worker role does not provide feedback within a certain timeout, the worker role ended suddenly, the request appears in the queue again and it is available for another worker role. [sent-36, score-0.966]

14 Performance - decomposition and distribution instead of stress The cloud architectures are quite sensitive to performance constraints inherent in the technology itself such as the non-proximity of resources, the commodity hardware or the resource sharing. [sent-37, score-0.88]

15 Rather than strengthen a single component of the architecture, the decomposition of the architecture in different modules deployed across multiple nodes is the key to improve the performance. [sent-40, score-0.458]

16 Reliability - MTTR instead of MTBF Traditionally, the reliability of an architecture is related to the concept of the MTBF, the mean time between a failure and another, in other words, how much wider the period the more reliable the system. [sent-47, score-0.571]

17 Capacity Planning - scale unit  planning  instead of  worst case planning The capacity planning in traditional architecture is designed to estimate the sizing required to support the maximum load so that the system is able to respond well enough even in the worst situations. [sent-54, score-1.093]

18 In contrast, the capacity planning in the cloud architecture is oriented to determine the scale unit, i. [sent-56, score-0.553]

19 We have seen how cloud architectures diverge from everything done in the past because it is necessarily respond to different scenarios. [sent-59, score-0.521]

20 Many of the approaches used in the past are no longer usable and the fundamental concepts underlying architectures such as scalability, performance, reliability, and capacity planning are deeply reviewed. [sent-60, score-0.681]


similar blogs computed by tfidf model

tfidf for this blog:

wordName wordTfidf (topN-words)

[('worker', 0.246), ('hw', 0.221), ('cloud', 0.211), ('architectures', 0.207), ('mttr', 0.183), ('architecture', 0.174), ('planning', 0.168), ('words', 0.159), ('commodity', 0.143), ('traditional', 0.14), ('unavailability', 0.136), ('must', 0.128), ('decomposition', 0.122), ('role', 0.114), ('concepts', 0.113), ('longer', 0.111), ('respond', 0.103), ('able', 0.103), ('instead', 0.099), ('resource', 0.098), ('according', 0.097), ('nodes', 0.094), ('resources', 0.092), ('concept', 0.089), ('resilient', 0.083), ('resilience', 0.083), ('usable', 0.082), ('adapt', 0.081), ('criteria', 0.078), ('provisioning', 0.075), ('worst', 0.075), ('reliability', 0.075), ('exceptional', 0.074), ('reliable', 0.071), ('essays', 0.068), ('subdivide', 0.068), ('failurethe', 0.068), ('strengthen', 0.068), ('anyways', 0.068), ('design', 0.068), ('application', 0.065), ('unit', 0.065), ('leads', 0.064), ('redefines', 0.064), ('breakdowns', 0.064), ('reid', 0.064), ('redefining', 0.064), ('failure', 0.063), ('maximum', 0.063), ('rules', 0.061)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.99999976 1654 high scalability-2014-06-05-Cloud Architecture Revolution

Introduction: The introduction of cloud technologies is not a simple evolution of existing ones, but a real revolution.  Like all revolutions, it changes the points of views and redefines all the meanings. Nothing is as before.  This post wants to analyze some key words and concepts, usually used in traditional architectures, redefining them according the standpoint of the cloud.  Understanding the meaning of new words is crucial to grasp the essence of a pure cloud architecture. << There is no greater impediment to the advancement of knowledge than the ambiguity of words. >> THOMAS REID, Essays on the Intellectual Powers of Man Nowadays, it is required to challenge the limits of traditional architectures that go beyond the normal concepts of scalability and support millions of users (What's Up 500 Million) billions of transactions per day (Salesforce 1.3 billion), five 9s of availability (99.999 AOL).  I wish all of you the success of the examples cited above, but do not think that it is co

2 0.18558706 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?

Introduction: We are on the edge of two potent technological changes: Clouds and Memory Based Architectures. This evolution will rip open a chasm where new players can enter and prosper. Google is the master of disk. You can't beat them at a game they perfected. Disk based databases like SimpleDB and BigTable are complicated beasts, typical last gasp products of any aging technology before a change. The next era is the age of Memory and Cloud which will allow for new players to succeed. The tipping point will be soon. Let's take a short trip down web architecture lane: It's 1993: Yahoo runs on FreeBSD, Apache, Perl scripts and a SQL database It's 1995: Scale-up the database. It's 1998: LAMP It's 1999: Stateless + Load Balanced + Database + SAN It's 2001: In-memory data-grid. It's 2003: Add a caching layer. It's 2004: Add scale-out and partitioning. It's 2005: Add asynchronous job scheduling and maybe a distributed file system. It's 2007: Move it all into the cloud. It's 2008: C

3 0.17897134 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT

Introduction: It remains that, from the same principles, I now demonstrate the frame of the System of the World. -- Isaac Newton The practice of IT reminds me a lot of the practice of science before Isaac Newton. Aristotelianism was dead, but there was nothing to replace it. Then Newton came along, created a scientific revolution with his System of the World . And everything changed. That was New System of the World number one. New System of the World number two was written about by the incomparable Neal Stephenson in his incredible  Baroque Cycle  series. It explores the singular creation of a new way of organizing society grounded in new modes of thought in business, religion, politics, and science. Our modern world emerged Enlightened as it could from this roiling cauldron of forces. In IT we may have had a Leonardo da Vinci or even a Galileo, but we’ve never had our Newton. Maybe we don't need a towering genius to make everything clear? For years startups, like the frenetically inventive

4 0.17497262 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud

Introduction: "But it is not complicated. [There's] just a lot of it." \--Richard Feynmanon how the immense variety of the world arises from simple rules.Contents:Have We Reached the End of Scaling?Applications Become Black Boxes Using Markets to Scale and Control CostsLet's Welcome our Neo-Feudal OverlordsThe Economic Argument for the Ambient CloudWhat Will Kill the Cloud?The Amazing Collective Compute Power of the Ambient CloudUsing the Ambient Cloud as an Application RuntimeApplications as Virtual StatesConclusionWe have not yet begun to scale. The world is still fundamentally disconnected and for all our wisdom we are still in the earliest days of learning how to build truly large planet-scaling applications.Today 350 million users on Facebook is a lot of users and five million followers on Twitter is a lot of followers. This may seem like a lot now, but consider we have no planet wide applications yet. None.Tomorrow the numbers foreshadow a newCambrian explosionof connectivity that will look as

5 0.17494777 1355 high scalability-2012-11-05-Gone Fishin': Building Super Scalable Systems: Blade Runner Meets Autonomic Computing In The Ambient Cloud

Introduction: All in all this is still my favorite post and I still think it's an accurate vision of a future. Not everyone agrees, but I guess we'll see..."But it is not complicated. [There's] just a lot of it." \--Richard Feynmanon how the immense variety of the world arises from simple rules.Contents:Have We Reached the End of Scaling?Applications Become Black Boxes Using Markets to Scale and Control CostsLet's Welcome our Neo-Feudal OverlordsThe Economic Argument for the Ambient CloudWhat Will Kill the Cloud?The Amazing Collective Compute Power of the Ambient CloudUsing the Ambient Cloud as an Application RuntimeApplications as Virtual StatesConclusionWe have not yet begun to scale. The world is still fundamentally disconnected and for all our wisdom we are still in the earliest days of learning how to build truly large planet-scaling applications.Today 350 million users on Facebook is a lot of users and five million followers on Twitter is a lot of followers. This may seem like a lot now, but c

6 0.17330751 643 high scalability-2009-06-29-How to Succeed at Capacity Planning Without Really Trying : An Interview with Flickr's John Allspaw on His New Book

7 0.16852224 853 high scalability-2010-07-08-Cloud AWS Infrastructure vs. Physical Infrastructure

8 0.15513475 674 high scalability-2009-08-07-The Canonical Cloud Architecture

9 0.1448101 761 high scalability-2010-01-17-Applications Become Black Boxes Using Markets to Scale and Control Costs

10 0.14375421 1258 high scalability-2012-06-05-Thesis: Concurrent Programming for Scalable Web Architectures

11 0.13650714 881 high scalability-2010-08-16-Scaling an AWS infrastructure - Tools and Patterns

12 0.13375957 96 high scalability-2007-09-18-Amazon Architecture

13 0.13304056 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO

14 0.13072266 920 high scalability-2010-10-15-Troubles with Sharding - What can we learn from the Foursquare Incident?

15 0.13055797 1604 high scalability-2014-03-03-The “Four Hamiltons” Framework for Mitigating Faults in the Cloud: Avoid it, Mask it, Bound it, Fix it Fast

16 0.12736335 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture

17 0.12721361 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010

18 0.12618645 1413 high scalability-2013-02-27-42 Monster Problems that Attack as Loads Increase

19 0.12470147 786 high scalability-2010-03-02-Using the Ambient Cloud as an Application Runtime

20 0.1220151 918 high scalability-2010-10-12-The CIO’s Problem: Cloud “Mess” or Cloud “Mash”


similar blogs computed by lsi model

lsi for this blog:

topicId topicWeight

[(0, 0.259), (1, 0.087), (2, 0.052), (3, 0.068), (4, -0.083), (5, -0.047), (6, 0.046), (7, -0.081), (8, -0.062), (9, -0.017), (10, -0.021), (11, 0.063), (12, -0.035), (13, 0.051), (14, -0.002), (15, -0.043), (16, 0.06), (17, -0.017), (18, 0.015), (19, 0.014), (20, -0.011), (21, 0.027), (22, -0.036), (23, 0.02), (24, 0.014), (25, -0.025), (26, -0.041), (27, 0.031), (28, 0.041), (29, 0.071), (30, 0.043), (31, 0.013), (32, 0.039), (33, -0.006), (34, -0.01), (35, 0.049), (36, -0.04), (37, -0.051), (38, -0.03), (39, -0.043), (40, -0.032), (41, -0.016), (42, -0.029), (43, -0.013), (44, 0.002), (45, 0.014), (46, -0.06), (47, 0.001), (48, 0.001), (49, -0.001)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.9801982 1654 high scalability-2014-06-05-Cloud Architecture Revolution

Introduction: The introduction of cloud technologies is not a simple evolution of existing ones, but a real revolution.  Like all revolutions, it changes the points of views and redefines all the meanings. Nothing is as before.  This post wants to analyze some key words and concepts, usually used in traditional architectures, redefining them according the standpoint of the cloud.  Understanding the meaning of new words is crucial to grasp the essence of a pure cloud architecture. << There is no greater impediment to the advancement of knowledge than the ambiguity of words. >> THOMAS REID, Essays on the Intellectual Powers of Man Nowadays, it is required to challenge the limits of traditional architectures that go beyond the normal concepts of scalability and support millions of users (What's Up 500 Million) billions of transactions per day (Salesforce 1.3 billion), five 9s of availability (99.999 AOL).  I wish all of you the success of the examples cited above, but do not think that it is co

2 0.80259126 381 high scalability-2008-09-08-Guerrilla Capacity Planning and the Law of Universal Scalability

Introduction: In the era of Web 2.0 traditional approaches to capacity planning are often difficult to implement. Guerrilla Capacity Planning facilitates rapid forecasting of capacity requirements based on the opportunistic use of whatever performance data and tools are available. One unique Guerrilla tool is Virtual Load Testing, based on Dr. Gunther's "Universal Law of Computational Scaling", which provides a highly cost-effective method for assessing application scalability. Neil Gunther, M.Sc., Ph.D. is an internationally recognized computer system performance consultant who founded Performance Dynamics Company in 1994. Some reasons why you should understand this law: 1. A lot of people use the term "scalability" without clearly defining it, let alone defining it quantitatively. Computer system scalability must be quantified. If you can't quantify it, you can't guarantee it. The universal law of computational scaling provides that quantification. 2. One the greatest impediments to applying

3 0.79381233 702 high scalability-2009-09-11-The interactive cloud

Introduction: How many times have you been called in the middle of the night by your operation guys telling you that your application throws some odd red alerts? How many times did you found out that when those issues happens you don't have enough information to analyze this incident? have you tried to increase the log level just to find out that your problem became even worse - now your application throws tons of information in a continues basis most of which is complete garbage... The current separation between the way we implement our application and the way we manage it leads to many of this ridicules situations. Cloud makes those things even worse. In this post i suggest an alternative approach. Why don't we run our application the way we run our business? I refer to this approach as the "interactive cloud" where our application behaves just like our project team and the operations just like our managers. As with our business our application would need to take more responsibility to the wa

4 0.78162414 694 high scalability-2009-09-04-Hot Links for 2009-9-4

Introduction: A tour through hybrid column/row-oriented DBMS schemes by DANIEL ABADI. Approaches: PAX, Fractured Mirrors, and Fine-grained hybrids. The Future of Database Clustering by ROBERT HODGES. Simple management and monitoring, Fast, flexible replication, Top-to-bottom data protection, Partition management, Cloud and virtualized operation, Transparent application access, Open source . Some perspective to this DIY storage server mentioned at Storagemojo by Joerg Moellenkamp. Quality costs. Period. Turn up the volume: API Scalability with Caching by Scott. Disk I/O Bottlenecks by Ryan Thiessen. My first approach to diagnosing a performance problem is to start by trying to find the system’s bottleneck . Patterns for Cloud Computing by Simon Guest. Using the Cloud for Scale, Using the Cloud for Multi-Tenancy, Using the Cloud for Compute, Using the Cloud for Storage, Using the Cloud for Communications Server Processor Roadmaps Show Change in Direction By Michael

5 0.78121805 1182 high scalability-2012-01-27-Stuff The Internet Says On Scalability For January 27, 2012

Introduction: If you’ve got the time, we’ve got the HighScalability: 9nm : IBM's carbon nanotube transistor that outperforms silicon; YouTube : 4 Billion Views/Day; 864GB RAM : 37signals Memcache, $12K Quotable Quotes: Chad Dickerson : You can only get growth by feeding opportunities. @launchany : It amazes me how many NoSQL database vendors spend more time detailing their scalability and no time detailing the data model and design Google : Let's make TCP faster. WhatsApp : we are now able to easily push our systems to over 2 million tcp connections! Sidney Dekker : In a complex system…doing the same thing twice will not predictably or necessarily lead to the same results. @Rasmusfjord : Just heard about an Umbraco site running on Azure that handles 20.000 requests /*second* Herb Sutter with an epic post,  Welcome to the Jungle , touching on a lot of themes we've explored on HighScalability, only in a dramatically more competent way. What's after

6 0.78102154 674 high scalability-2009-08-07-The Canonical Cloud Architecture

7 0.78072166 1184 high scalability-2012-01-31-Performance in the Cloud: Business Jitter is Bad

8 0.78067023 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010

9 0.77975124 1056 high scalability-2011-06-09-Retrospect on recent AWS outage and Resilient Cloud-Based Architecture

10 0.7795645 1006 high scalability-2011-03-17-Are long VM instance spin-up times in the cloud costing you money?

11 0.77766556 1212 high scalability-2012-03-21-The Conspecific Hybrid Cloud

12 0.77595228 1354 high scalability-2012-11-05-Are we seeing the renaissance of enterprises in the cloud?

13 0.76270539 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT

14 0.76138818 953 high scalability-2010-12-03-GPU vs CPU Smackdown : The Rise of Throughput-Oriented Architectures

15 0.76033688 1411 high scalability-2013-02-22-Stuff The Internet Says On Scalability For February 22, 2013

16 0.75903386 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture

17 0.75869524 1206 high scalability-2012-03-09-Stuff The Internet Says On Scalability For March 9, 2012

18 0.75462544 1127 high scalability-2011-09-28-Pursue robust indefinite scalability with the Movable Feast Machine

19 0.7543903 407 high scalability-2008-10-10-The Art of Capacity Planning: Scaling Web Resources

20 0.75147218 428 high scalability-2008-10-24-11 Secrets of a Cloud Scale Consultant That They Dont' Want You to Know


similar blogs computed by lda model

lda for this blog:

topicId topicWeight

[(1, 0.138), (2, 0.191), (10, 0.071), (17, 0.011), (18, 0.125), (30, 0.04), (47, 0.02), (56, 0.013), (61, 0.075), (79, 0.156), (85, 0.02), (94, 0.057)]

similar blogs list:

simIndex simValue blogId blogTitle

1 0.97179037 1140 high scalability-2011-11-10-Kill the Telcos Save the Internet - The Unsocial Network

Introduction: Someone is killing the Internet. Since you probably use the Internet everyday you might find this surprising. It almost sounds silly, and the reason is technical, but our crack team of networking experts has examined the patient and made the diagnosis. What did they find? Diagnostic team : the  Packet Pushers  gang ( Greg Ferro , Jan Zorz , Ivan Pepelnjak ) in the podcast  How We Are Killing the Internet . Diagnosis : invasive tunnelation. ( tubes anyone? ) Prognosis : even Dr. House might not be able to help. Cure : go back to what the Internet was; kill the tunnels; route IPv4 and IPv6; have public addresses on everything; disrupt the telcos. This is a classic story in a strange setting--the network--but the themes are universal: centralization vs. decentralization (that's where the telcos obviously come in), good vs. evil, order vs. disorder, tyranny vs. freedom, change vs. stasis, simplicity vs. complexity. And it's all being carried out on battlefield few get

2 0.95186985 1344 high scalability-2012-10-19-Stuff The Internet Says On Scalability For October 19, 2012

Introduction: It's HighScalability Time: @davilagrau : Youtube, GitHub,..., Are cloud services facing a entropic limit to scalability? Async all the way down?  The Tyranny of the Clock : The cost of logic and memory dominated Turing's thinking, but today, communication rather than logic should dominate our thinking. Clock-free design uses less than half, about 40%, as much energy per addition as its clocked counterpart. We can regain the efficiency of local decision making by revolting against the pervasive beat of an external clock.  Why Google Compute Engine for OpenStack . Smart move. Having OpenStack work inside a super charged cloud, in private clouds, and as a bridge between the two ought to be quite attractive to developers looking for some sort of ally for independence. All it will take are a few victories to cement new alliances. 3 Lessons That Startups Can Learn From Facebook’s Failed Credits Experiment . I thought this was a great idea too. So what happened? FACEBOOK DID NOT

same-blog 3 0.9370926 1654 high scalability-2014-06-05-Cloud Architecture Revolution

Introduction: The introduction of cloud technologies is not a simple evolution of existing ones, but a real revolution.  Like all revolutions, it changes the points of views and redefines all the meanings. Nothing is as before.  This post wants to analyze some key words and concepts, usually used in traditional architectures, redefining them according the standpoint of the cloud.  Understanding the meaning of new words is crucial to grasp the essence of a pure cloud architecture. << There is no greater impediment to the advancement of knowledge than the ambiguity of words. >> THOMAS REID, Essays on the Intellectual Powers of Man Nowadays, it is required to challenge the limits of traditional architectures that go beyond the normal concepts of scalability and support millions of users (What's Up 500 Million) billions of transactions per day (Salesforce 1.3 billion), five 9s of availability (99.999 AOL).  I wish all of you the success of the examples cited above, but do not think that it is co

4 0.93572968 139 high scalability-2007-10-30-Paper: Dynamo: Amazon’s Highly Available Key-value Store

Introduction: Update 2 : Read/WriteWeb has a good article talking about the scalability issues of relational databases and how Dynamo solves them: Amazon Dynamo: The Next Generation Of Virtual Distributed Storage . But since Dynamo is just another frustrating walled garden protected by barbed wire and guard dogs, its relevance is somewhat overstated. Update : Greg Linden has a take on the paper where he questions some of Amazon's design choices: emphasizing write availability over fast reads, a lack of indexing support, use of random distribution for load balancing, and punting on some scalability issues. Werner Vogels, Amazon's avuncular CTO, just announced a new paper on the internal database technology Amazon uses to handle tens of millions customers. I'll dive into more details later, but I thought you'd want to read it hot off the blog. The bad news is it won't be a service. They are keeping this tech not so secret, but very safe. Happily, it's another real-life example to learn from.

5 0.91222405 289 high scalability-2008-03-27-Amazon Announces Static IP Addresses and Multiple Datacenter Operation

Introduction: Amazon is fixing two of their major problems: no static IP addresses and single datacenter operation. By adding these two new features developers can finally build a no apology system on Amazon. Before you always had to throw in an apology or two. No, we don't have low failover times because of the silly DNS games and unexceptionable DNS update and propagation times and no, we don't operate in more than one datacenter. No more. Now Amazon is adding Elastic IP Addresses and Availability Zones . Elastic IP addresses are far better than normal IP addresses because they are both in tight with Jessica Alba and they are: Static IP addresses designed for dynamic cloud computing. An Elastic IP address is associated with your account, not a particular instance, and you control that address until you choose to explicitly release it. Unlike traditional static IP addresses, however, Elastic IP addresses allow you to mask instance or availability zone failures by programmatica

6 0.91137999 195 high scalability-2007-12-28-Amazon's EC2: Pay as You Grow Could Cut Your Costs in Half

7 0.90943688 1186 high scalability-2012-02-02-The Data-Scope Project - 6PB storage, 500GBytes-sec sequential IO, 20M IOPS, 130TFlops

8 0.90852332 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)

9 0.90837067 716 high scalability-2009-10-06-Building a Unique Data Warehouse

10 0.90737301 129 high scalability-2007-10-23-Hire Facebook, Ning, and Salesforce to Scale for You

11 0.90661943 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud

12 0.90656042 1355 high scalability-2012-11-05-Gone Fishin': Building Super Scalable Systems: Blade Runner Meets Autonomic Computing In The Ambient Cloud

13 0.90617794 1041 high scalability-2011-05-15-Building a Database remote availability site

14 0.90541911 776 high scalability-2010-02-12-Hot Scalability Links for February 12, 2010

15 0.90541047 857 high scalability-2010-07-13-DbShards Part Deux - The Internals

16 0.9053914 763 high scalability-2010-01-22-How BuddyPoke Scales on Facebook Using Google App Engine

17 0.90520179 1649 high scalability-2014-05-16-Stuff The Internet Says On Scalability For May 16th, 2014

18 0.90498048 576 high scalability-2009-04-21-What CDN would you recommend?

19 0.9043861 761 high scalability-2010-01-17-Applications Become Black Boxes Using Markets to Scale and Control Costs

20 0.90385932 851 high scalability-2010-07-02-Hot Scalability Links for July 2, 2010