high_scalability high_scalability-2010 high_scalability-2010-960 knowledge-graph by maker-knowledge-mining

960 high scalability-2010-12-20-Netflix: Use Less Chatty Protocols in the Cloud - Plus 26 Fixes


meta infos for this blog

Source: html

Introduction: In  5 Lessons We’ve Learned Using AWS , Netflix's John Ciancutti says one of the big lessons they've learned is to create less chatty protocols : In the Netflix data centers, we have a high capacity, super fast, highly reliable network. This has afforded us the luxury of designing around chatty APIs to remote systems. AWS networking has more variable latency. We’ve had to be much more structured about “over the wire” interactions, even as we’ve transitioned to a more highly distributed architecture. There's not a lot of advice out there on how to create protocols. Combine that with a rush to the cloud and you have a perfect storm for chatty applications crushing application performance. Netflix is far from the first to be surprised by the less than stellar networks inside AWS.  A chatty protocol is one where a client makes a series of requests to a server and the client must wait on each reply before sending the next request. On a LAN this can work great. LAN's are typically


Summary: the most important sentenses genereted by tfidf model

sentIndex sentText sentNum sentScore

1 In  5 Lessons We’ve Learned Using AWS , Netflix's John Ciancutti says one of the big lessons they've learned is to create less chatty protocols : In the Netflix data centers, we have a high capacity, super fast, highly reliable network. [sent-1, score-0.57]

2 This has afforded us the luxury of designing around chatty APIs to remote systems. [sent-2, score-0.506]

3 A chatty protocol is one where a client makes a series of requests to a server and the client must wait on each reply before sending the next request. [sent-8, score-0.885]

4 The overall goal is to reduce the number of times a client has to wait for a response and reduce the number of packets sent. [sent-19, score-0.384]

5 This may be obvious, but take a look at your protocols and see if any of the rountrips can be combined or eliminated. [sent-23, score-0.358]

6 One of the reasons protocols become so chatty is programmers are thinking in terms of fine-grained distributed objects rather coarser-grained services. [sent-26, score-0.612]

7 This leads to chatty protocols because there is a lot of back and forth for each method call as methods tend to be pretty low in granularity. [sent-27, score-0.586]

8 To transform an image, for example, you want to make one call and pass in all the transforms so they can be done in that one call rather than making a separate remote method invocation for each transform. [sent-29, score-0.264]

9 Queue up requests for X milliseconds so they can be sent in a batch rather than one by one. [sent-37, score-0.324]

10 Please, no flamewars, but a custom binary protocol will generally be more space efficient than text + compression. [sent-44, score-0.236]

11 Allow requests to reuse recently transmitted information . [sent-49, score-0.233]

12 When configuration is needed try to do it in bulk so that a program will get all it's configuration attributes in one big structure rather than making a lot of individual calls. [sent-64, score-0.425]

13 Another approach is to use lazy initialization so you just get configuration as needed rather than all at once. [sent-65, score-0.265]

14 Don't, for example, implement a drag and drop operation over the network that can take 100s of requests to implement. [sent-77, score-0.228]

15 Older versions of Windows would go get the directory on the remote side and for every file it would perform individual file stat operations for each file attribute. [sent-78, score-0.374]

16 What a WAN accelerator does is get all the file data at once, create a local cache, and serve those requests from the local cache. [sent-79, score-0.298]

17 Hopefully in the future the L2/L3 network fabrics inside datacenters will improve as will datacenter interconnects. [sent-96, score-0.192]

18 Since this will drive up payload sizes, they will try using  partial response s as a counter measure. [sent-108, score-0.247]

19 A partial response is like a SQL select statement where you can specify only the fields you want back. [sent-111, score-0.217]

20 So the goal is reduce payload sizes by being more selective about what data is returned. [sent-113, score-0.273]


similar blogs computed by tfidf model

tfidf for this blog:

wordName wordTfidf (topN-words)

[('chatty', 0.357), ('wan', 0.167), ('protocol', 0.165), ('protocols', 0.145), ('rountrips', 0.145), ('requests', 0.133), ('client', 0.115), ('rather', 0.11), ('token', 0.11), ('payload', 0.104), ('netflix', 0.103), ('reduce', 0.1), ('transmitted', 0.1), ('inside', 0.097), ('file', 0.097), ('lan', 0.096), ('fat', 0.096), ('network', 0.095), ('affinity', 0.09), ('configuration', 0.089), ('hpc', 0.087), ('grained', 0.085), ('forth', 0.084), ('remote', 0.083), ('sent', 0.081), ('amount', 0.077), ('window', 0.074), ('returned', 0.074), ('partial', 0.073), ('fields', 0.073), ('pass', 0.071), ('binary', 0.071), ('rack', 0.071), ('specify', 0.071), ('behavior', 0.07), ('try', 0.07), ('goal', 0.069), ('create', 0.068), ('combined', 0.068), ('bulk', 0.067), ('course', 0.066), ('initialization', 0.066), ('cifs', 0.066), ('corba', 0.066), ('pings', 0.066), ('afforded', 0.066), ('awan', 0.066), ('burstiness', 0.066), ('ciancutti', 0.066), ('collocating', 0.066)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.99999952 960 high scalability-2010-12-20-Netflix: Use Less Chatty Protocols in the Cloud - Plus 26 Fixes

Introduction: In  5 Lessons We’ve Learned Using AWS , Netflix's John Ciancutti says one of the big lessons they've learned is to create less chatty protocols : In the Netflix data centers, we have a high capacity, super fast, highly reliable network. This has afforded us the luxury of designing around chatty APIs to remote systems. AWS networking has more variable latency. We’ve had to be much more structured about “over the wire” interactions, even as we’ve transitioned to a more highly distributed architecture. There's not a lot of advice out there on how to create protocols. Combine that with a rush to the cloud and you have a perfect storm for chatty applications crushing application performance. Netflix is far from the first to be surprised by the less than stellar networks inside AWS.  A chatty protocol is one where a client makes a series of requests to a server and the client must wait on each reply before sending the next request. On a LAN this can work great. LAN's are typically

2 0.2594755 1001 high scalability-2011-03-09-Google and Netflix Strategy: Use Partial Responses to Reduce Request Sizes

Introduction: This strategy targets reducing the amount of protocol data in packets by sending only the attributes that are needed. Google calls this  Partial Response and Partial Update . Netflix posted about adopting this strategy in their  recent Netflix API redesign . We've seen previously how Netflix improved performance by creating less chatty protocols . As a consequence packet sizes rise as more data is being stuffed into each packet in order to reduce the number of round trips. But we don't like large packets either (memory usage and packet processing overhead), so we have to think of creative ways to shrink them back down. The change Netflx is making is to conceptualize their API as a database. What does this mean? A partial response is like a SQL select statement where you can specify only the fields you want back. Only the attributes of interest are requested.  Previously all fields for objects were returned, even if the client didn't need them. So the goal is reduce payload s

3 0.21257575 119 high scalability-2007-10-10-WAN Accelerate Your Way to Lightening Fast Transfers Between Data Centers

Introduction: How do you keep in sync a crescendo of data between data centers over a slow WAN? That's the question Alberto posted a few weeks ago. Normally I'm not into all boy bands, but I was frustrated there wasn't a really good answer for his problem. It occurred to me later a WAN accelerator might help turn his slow WAN link into more of a LAN, so the overhead of copying files across the WAN wouldn't be so limiting. Many might not consider a WAN accelerator in this situation, but since my friend Damon Ennis works at the WAN accelerator vendor Silver Peak , I thought I would ask him if their product would help. Not surprisingly his answer is yes! Potentially a lot, depending on the nature of your data. Here's a no BS overview of their product: What is it? - Scalable WAN Accelerator from Silver Peak (http://www.silver-peak.com) What does it do? - You can send 5x-100x times more data across your expensive, low-bandwidth WAN link. Why should you care? - Your data centers becom

4 0.19425617 645 high scalability-2009-06-30-Hot New Trend: Linking Clouds Through Cheap IP VPNs Instead of Private Lines

Introduction: You might think major Internet companies have a latency, availability, and bandwidth advantage because they can afford expensive dedicated point-to-point private line networks between their data centers. And you would be right. It's a great advantage. Or it at least it was a great advantage. Cost is the great equalizer and companies are now scrambling for ways to cut costs. Many of the most recognizable Internet companies are moving to IP VPNs (Virtual Private Networks) as a much cheaper alternative to private lines. This is a strategy you can effectively use too. This trend has historical precedent in the data center. In the same way leading edge companies moved early to virtualize their data centers, leading edge companies are now virtualizing their networks using IP VPNs to build inexpensive private networks over a shared public network. In kindergarten we learned sharing was polite, it turns out sharing can also save a lot of money in both the data center and on the network. The

5 0.18681511 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

6 0.17616795 1413 high scalability-2013-02-27-42 Monster Problems that Attack as Loads Increase

7 0.16231483 1421 high scalability-2013-03-11-Low Level Scalability Solutions - The Conditioning Collection

8 0.15587358 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results

9 0.14859401 1266 high scalability-2012-06-18-Google on Latency Tolerant Systems: Making a Predictable Whole Out of Unpredictable Parts

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

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

12 0.13767569 1565 high scalability-2013-12-16-22 Recommendations for Building Effective High Traffic Web Software

13 0.13635738 1501 high scalability-2013-08-13-In Memoriam: Lavabit Architecture - Creating a Scalable Email Service

14 0.13184577 881 high scalability-2010-08-16-Scaling an AWS infrastructure - Tools and Patterns

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

16 0.13117182 205 high scalability-2008-01-10-Letting Clients Know What's Changed: Push Me or Pull Me?

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

18 0.12903145 1596 high scalability-2014-02-14-Stuff The Internet Says On Scalability For February 14th, 2014

19 0.12834889 780 high scalability-2010-02-19-Twitter’s Plan to Analyze 100 Billion Tweets

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


similar blogs computed by lsi model

lsi for this blog:

topicId topicWeight

[(0, 0.26), (1, 0.148), (2, -0.029), (3, 0.005), (4, -0.054), (5, -0.01), (6, 0.105), (7, 0.071), (8, -0.107), (9, -0.044), (10, 0.02), (11, 0.044), (12, -0.032), (13, -0.044), (14, 0.038), (15, 0.02), (16, 0.065), (17, 0.041), (18, -0.008), (19, -0.044), (20, 0.026), (21, -0.015), (22, 0.068), (23, 0.019), (24, 0.015), (25, 0.055), (26, 0.048), (27, 0.02), (28, 0.018), (29, -0.067), (30, 0.001), (31, -0.058), (32, 0.02), (33, 0.061), (34, 0.021), (35, 0.079), (36, 0.041), (37, 0.053), (38, -0.052), (39, -0.056), (40, 0.007), (41, 0.023), (42, -0.013), (43, -0.055), (44, 0.002), (45, -0.039), (46, -0.015), (47, 0.024), (48, -0.119), (49, -0.014)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.96460104 960 high scalability-2010-12-20-Netflix: Use Less Chatty Protocols in the Cloud - Plus 26 Fixes

Introduction: In  5 Lessons We’ve Learned Using AWS , Netflix's John Ciancutti says one of the big lessons they've learned is to create less chatty protocols : In the Netflix data centers, we have a high capacity, super fast, highly reliable network. This has afforded us the luxury of designing around chatty APIs to remote systems. AWS networking has more variable latency. We’ve had to be much more structured about “over the wire” interactions, even as we’ve transitioned to a more highly distributed architecture. There's not a lot of advice out there on how to create protocols. Combine that with a rush to the cloud and you have a perfect storm for chatty applications crushing application performance. Netflix is far from the first to be surprised by the less than stellar networks inside AWS.  A chatty protocol is one where a client makes a series of requests to a server and the client must wait on each reply before sending the next request. On a LAN this can work great. LAN's are typically

2 0.82291734 1051 high scalability-2011-06-01-Why is your network so slow? Your switch should tell you.

Introduction: Who hasn't cursed their network for being slow while waiting for that annoying little hour glass of pain to release all its grains of sand? But what's really going on? Is your network really slow? PacketPushers  Show 45 – Arista – EOS Network Software Architecture  has a good explanation of what may be really at fault (paraphrased): Network operators get calls from application guys saying the network is slow, but the problem is usually dropped packets due to congestion. It's not usually latency, it's usually packet loss. Packet loss causes TCP to back off and retransmit, which causes applications to appear slow. Packet loss can be caused by a flakey transceiver, but the problem is usually network congestion. Somewhere on the network there's fan-in, a bottleneck develops, queues build up to a certain point, and when a queue overflows it drops packets. Often the first sign of this happening is application slowness. Queues get deeper and deeper because the network is getting more

3 0.81809098 1001 high scalability-2011-03-09-Google and Netflix Strategy: Use Partial Responses to Reduce Request Sizes

Introduction: This strategy targets reducing the amount of protocol data in packets by sending only the attributes that are needed. Google calls this  Partial Response and Partial Update . Netflix posted about adopting this strategy in their  recent Netflix API redesign . We've seen previously how Netflix improved performance by creating less chatty protocols . As a consequence packet sizes rise as more data is being stuffed into each packet in order to reduce the number of round trips. But we don't like large packets either (memory usage and packet processing overhead), so we have to think of creative ways to shrink them back down. The change Netflx is making is to conceptualize their API as a database. What does this mean? A partial response is like a SQL select statement where you can specify only the fields you want back. Only the attributes of interest are requested.  Previously all fields for objects were returned, even if the client didn't need them. So the goal is reduce payload s

4 0.8081851 645 high scalability-2009-06-30-Hot New Trend: Linking Clouds Through Cheap IP VPNs Instead of Private Lines

Introduction: You might think major Internet companies have a latency, availability, and bandwidth advantage because they can afford expensive dedicated point-to-point private line networks between their data centers. And you would be right. It's a great advantage. Or it at least it was a great advantage. Cost is the great equalizer and companies are now scrambling for ways to cut costs. Many of the most recognizable Internet companies are moving to IP VPNs (Virtual Private Networks) as a much cheaper alternative to private lines. This is a strategy you can effectively use too. This trend has historical precedent in the data center. In the same way leading edge companies moved early to virtualize their data centers, leading edge companies are now virtualizing their networks using IP VPNs to build inexpensive private networks over a shared public network. In kindergarten we learned sharing was polite, it turns out sharing can also save a lot of money in both the data center and on the network. The

5 0.80374777 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

6 0.77144367 1421 high scalability-2013-03-11-Low Level Scalability Solutions - The Conditioning Collection

7 0.75939214 205 high scalability-2008-01-10-Letting Clients Know What's Changed: Push Me or Pull Me?

8 0.75735939 266 high scalability-2008-03-04-Manage Downtime Risk by Connecting Multiple Data Centers into a Secure Virtual LAN

9 0.75707942 1048 high scalability-2011-05-27-Stuff The Internet Says On Scalability For May 27, 2011

10 0.75453538 1413 high scalability-2013-02-27-42 Monster Problems that Attack as Loads Increase

11 0.75339413 119 high scalability-2007-10-10-WAN Accelerate Your Way to Lightening Fast Transfers Between Data Centers

12 0.7451247 1140 high scalability-2011-11-10-Kill the Telcos Save the Internet - The Unsocial Network

13 0.73579723 1558 high scalability-2013-12-04-How Can Batching Requests Actually Reduce Latency?

14 0.73383164 1519 high scalability-2013-09-18-If You're Programming a Cell Phone Like a Server You're Doing it Wrong

15 0.72528982 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results

16 0.72483677 1267 high scalability-2012-06-18-The Clever Ways Chrome Hides Latency by Anticipating Your Every Need

17 0.72346729 1591 high scalability-2014-02-05-Little’s Law, Scalability and Fault Tolerance: The OS is your bottleneck. What you can do?

18 0.72329617 981 high scalability-2011-02-01-Google Strategy: Tree Distribution of Requests and Responses

19 0.71422929 343 high scalability-2008-06-09-Apple's iPhone to Use a Centralized Push Based Notification Architecture

20 0.71036398 1174 high scalability-2012-01-13-Stuff The Internet Says On Scalability For January 13, 2012


similar blogs computed by lda model

lda for this blog:

topicId topicWeight

[(1, 0.086), (2, 0.269), (4, 0.012), (5, 0.024), (10, 0.08), (23, 0.13), (30, 0.015), (40, 0.016), (47, 0.019), (49, 0.015), (61, 0.083), (79, 0.092), (85, 0.011), (94, 0.076)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.94400656 960 high scalability-2010-12-20-Netflix: Use Less Chatty Protocols in the Cloud - Plus 26 Fixes

Introduction: In  5 Lessons We’ve Learned Using AWS , Netflix's John Ciancutti says one of the big lessons they've learned is to create less chatty protocols : In the Netflix data centers, we have a high capacity, super fast, highly reliable network. This has afforded us the luxury of designing around chatty APIs to remote systems. AWS networking has more variable latency. We’ve had to be much more structured about “over the wire” interactions, even as we’ve transitioned to a more highly distributed architecture. There's not a lot of advice out there on how to create protocols. Combine that with a rush to the cloud and you have a perfect storm for chatty applications crushing application performance. Netflix is far from the first to be surprised by the less than stellar networks inside AWS.  A chatty protocol is one where a client makes a series of requests to a server and the client must wait on each reply before sending the next request. On a LAN this can work great. LAN's are typically

2 0.93845582 990 high scalability-2011-02-15-Wordnik - 10 million API Requests a Day on MongoDB and Scala

Introduction: Wordnik  is an online dictionary and language resource that has both a website and an API component. Their goal is to show you as much information as possible, as fast as we can find it, for every word in English, and to give you a place where you can make your own opinions about words known. As cool as that is, what is really cool is the information they share in their blog about their experiences building a web service. They've written an excellent series of articles and presentations you may find useful: What has technology do Save & Close ne for words lately? Eventual consistency . Using an eventually consistent model they can do work in parallel and we count as many words as possible when we can, and add them all up when there’s a lag. The count’s always in the ballpark, and we never have to stop .D Document-oriented storage . Dictionary entries are more naturally modeled as hierarchical documents and using that model has made it quicker to find data and is

3 0.93052238 1105 high scalability-2011-08-25-The Cloud and The Consumer: The Impact on Bandwidth and Broadband

Introduction: Cloud-based services for all things digital will either drive – or die by – bandwidth Consumers, by definition, consume. In the realm of the Internet, they consume far more than they produce. Or so it’s been in the past. Broadband connectivity across all providers have long offered asymmetric network feeds because it mirrored reality: an HTTP request is significantly smaller than its corresponding response, and in general web-based activity is heavily biased toward fat download and thin upload speeds. The term “broadband” is really a misnomer, as it focuses only on the download speed and ignores the very narrowband of a typical consumer’s upload speed. cloud computing , or to be more accurate, cloud-hosted services aimed at consumers may very well change the status quo by necessity. As providers continue to push the notion of storing all things digital “in the cloud”, network providers must consider the impact on them – and the satisfaction of their customer base with performa

4 0.92849821 979 high scalability-2011-01-27-Comet - An Example of the New Key-Code Databases

Introduction: Comet is an active distributed key-value store built at the University of Washington. The paper describing Comet is  Comet: An active distributed key-value store , there are also  slides , and a  MP3  of a presentation given at OSDI '10 . Here's a succinct  overview of Comet : Today's cloud storage services, such as Amazon S3 or peer-to-peer DHTs, are highly inflexible and impose a variety of constraints on their clients: specific replication and consistency schemes, fixed data timeouts, limited logging, etc. We witnessed such inflexibility first-hand as part of our Vanish work, where we used a DHT to store encryption keys temporarily. To address this issue, we built Comet, an extensible storage service that allows clients to inject snippets of code that control their data's behavior inside the storage service. I found this paper quite interesting because it takes the initial steps of collocating code with a key-value store, which turns it into what might called a  key-code

5 0.92672288 654 high scalability-2009-07-09-No to SQL? Anti-database movement gains steam – My Take

Introduction: In this post i wrote my view on the anti SQL database movement and where the alternative approach fits in: - SQL databases are not going away anytime soon. - The current "one size fit it all" databases thinking was and is wrong. - There is definitely a place for a more a more specialized data management solutions alongside traditional SQL databases. In addition to the options that was mentioned on the original article i pointed out the the in-memory alternative approach and how that fits into the puzzle. I used a real life scenario: scalable Social network based eCommerce site where i outlined how in-memory approach was the only option they could scale and meet their application performance and response time requirements.

6 0.91551805 554 high scalability-2009-04-04-Digg Architecture

7 0.9077757 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results

8 0.90740931 1010 high scalability-2011-03-24-Strategy: Disk Backup for Speed, Tape Backup to Save Your Bacon, Just Ask Google

9 0.90618801 1421 high scalability-2013-03-11-Low Level Scalability Solutions - The Conditioning Collection

10 0.90521336 1429 high scalability-2013-03-25-AppBackplane - A Framework for Supporting Multiple Application Architectures

11 0.90519416 533 high scalability-2009-03-11-The Implications of Punctuated Scalabilium for Website Architecture

12 0.90508103 221 high scalability-2008-01-24-Mailinator Architecture

13 0.90475374 556 high scalability-2009-04-05-At Some Point the Cost of Servers Outweighs the Cost of Programmers

14 0.90450501 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it

15 0.90410966 619 high scalability-2009-06-05-HotPads Shows the True Cost of Hosting on Amazon

16 0.903898 119 high scalability-2007-10-10-WAN Accelerate Your Way to Lightening Fast Transfers Between Data Centers

17 0.90339506 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture

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

19 0.90280819 306 high scalability-2008-04-21-The Search for the Source of Data - How SimpleDB Differs from a RDBMS

20 0.90248322 1407 high scalability-2013-02-15-Stuff The Internet Says On Scalability For February 15, 2013