high_scalability high_scalability-2007 high_scalability-2007-113 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: The article describes the basic architecture of a connection-oriented NIO-based java server. It takes a look at a preferred threading model, Java Non-blocking I/O and discusses the basic components of such a server.
sentIndex sentText sentNum sentScore
1 The article describes the basic architecture of a connection-oriented NIO-based java server. [sent-1, score-1.309]
2 It takes a look at a preferred threading model, Java Non-blocking I/O and discusses the basic components of such a server. [sent-2, score-1.974]
wordName wordTfidf (topN-words)
[('basic', 0.464), ('preferred', 0.394), ('threading', 0.348), ('discusses', 0.343), ('java', 0.298), ('blocking', 0.296), ('describes', 0.282), ('components', 0.182), ('article', 0.164), ('takes', 0.145), ('model', 0.133), ('architecture', 0.101), ('based', 0.098), ('look', 0.098), ('server', 0.079)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000001 113 high scalability-2007-10-07-Paper: Architecture of a Highly Scalable NIO-Based Server
Introduction: The article describes the basic architecture of a connection-oriented NIO-based java server. It takes a look at a preferred threading model, Java Non-blocking I/O and discusses the basic components of such a server.
2 0.17587155 459 high scalability-2008-12-03-Java World Interview on Scalability and Other Java Scalability Secrets
Introduction: OK, this interview is with me on Java scalability issues. I sound like a bigger idiot than I would like, but I suppose it could have been worse. The Java World folks were very nice and did a good job, so there’s no blame on them :-) The interview went an interesting direction, but there’s more I’d like add and I will do so here. Two major rules regarding Java and scalability have popped out at me: Java – It’s the platform stupid . Java the language isn’t the big win. What is the big win is the ecosystem building up around the JVM, libraries, and toolsets. Java – It’s the community stupid . A lot of creativity is being expended on leveraging the Java platform to meet scalability challenges. The amazing community that has built up around Java is pushing Java to the next level in almost every direction imaginable. The fecundity of the Java ecosystem can most readily be seen with the efforts to tame our multi-core future. There’s a multi-core crisis going in case you haven’t
Introduction: PayPal gives yet another glowing report of an app rewritten in node.js experiencing substantial performance improvements. PayPal rewrote their account overview page, one of the most trafficked apps on the website, which was previously written in King Java. The benefits: Full-stack engineers. Using JavaScript on both the front-end and the back-end removed an artificial boundary between the browser and server, allowing engineers to code both. Built almost twice as fast with fewer people Written in 33% fewer lines of code Constructed with 40% fewer files Double the requests per second vs. the Java application. 35% decrease in the average response time for the same page. A common pro Java response is an argument like clearly these people don't know how to program Java. Or rewriting an application usually makes it faster. Or the benchmark is faulty. And so on. Consider it noted. These are all potential factors. Baron Schwartz from VividCortex has a different tak
4 0.1245591 85 high scalability-2007-09-08-Making the case for PHP at Yahoo! (Oct 2002)
Introduction: This presentation by Michael Radwin describes why Yahoo! had standardized on PHP going forward. It describes how after reviewing all the web technologies including their own internal ones, PHP was choosen. It shows that not only technical reasons , but also business and development processes were taken into account.
5 0.12358789 653 high scalability-2009-07-08-Servers Component - How to choice and build perfect server
Introduction: There are a lot of questions about how the server components, and how to build perfect server with consider the power consumption. Today I will discuss the Server components, and how we can choice better server components with consider the power consumption, efficacy, performance, and price. Key points: What kind of components the servers needs? The Green Computing and the Servers components How much power the server consume Choice the right components: Processor Hard Disk Drive Memory Operating system Build Server, or buy?
6 0.11656207 550 high scalability-2009-03-30-Ebay history and architecture
7 0.10522369 585 high scalability-2009-04-29-How to choice and build perfect server
8 0.10183907 494 high scalability-2009-01-16-Reducing Your Website's Bandwidth Usage - how to
9 0.10103923 1118 high scalability-2011-09-19-Big Iron Returns with BigMemory
10 0.099186286 681 high scalability-2009-08-16-TechDev Stages
11 0.088192672 426 high scalability-2008-10-22-Server load balancing architectures, Part 1: Transport-level load balancing
12 0.08468809 364 high scalability-2008-08-14-Product: Terracotta - Open Source Network-Attached Memory
13 0.081936218 471 high scalability-2008-12-19-Gigaspaces curbs latency outliers with Java Real Time
14 0.081571445 454 high scalability-2008-12-01-Deploying MySQL Database in Solaris Cluster Environments
15 0.080698118 420 high scalability-2008-10-15-Tokyo Tech Tsubame Grid Storage Implementation
16 0.068993226 317 high scalability-2008-05-10-Hitting 300 SimbleDB Requests Per Second on a Small EC2 Instance
17 0.067879908 121 high scalability-2007-10-14-Newbie in scalability design issues
18 0.066323087 410 high scalability-2008-10-13-SQL Server 2008 Database Performance and Scalability
19 0.066001356 186 high scalability-2007-12-13-un-article: the setup behind microsoft.com
20 0.065420173 161 high scalability-2007-11-20-Product: SmartFrog a Distributed Configuration and Deployment Framework
topicId topicWeight
[(0, 0.074), (1, 0.009), (2, -0.011), (3, 0.011), (4, 0.007), (5, 0.027), (6, 0.011), (7, -0.011), (8, -0.054), (9, 0.072), (10, -0.019), (11, 0.021), (12, 0.048), (13, -0.011), (14, -0.036), (15, -0.028), (16, 0.028), (17, -0.015), (18, -0.002), (19, -0.047), (20, -0.014), (21, -0.077), (22, -0.018), (23, -0.083), (24, 0.001), (25, -0.039), (26, 0.031), (27, -0.088), (28, 0.046), (29, 0.007), (30, 0.003), (31, 0.028), (32, 0.008), (33, -0.034), (34, -0.01), (35, -0.04), (36, 0.046), (37, 0.033), (38, 0.003), (39, -0.032), (40, 0.009), (41, -0.004), (42, -0.045), (43, 0.029), (44, 0.033), (45, -0.045), (46, 0.154), (47, 0.027), (48, -0.035), (49, 0.022)]
simIndex simValue blogId blogTitle
same-blog 1 0.9891476 113 high scalability-2007-10-07-Paper: Architecture of a Highly Scalable NIO-Based Server
Introduction: The article describes the basic architecture of a connection-oriented NIO-based java server. It takes a look at a preferred threading model, Java Non-blocking I/O and discusses the basic components of such a server.
Introduction: PayPal gives yet another glowing report of an app rewritten in node.js experiencing substantial performance improvements. PayPal rewrote their account overview page, one of the most trafficked apps on the website, which was previously written in King Java. The benefits: Full-stack engineers. Using JavaScript on both the front-end and the back-end removed an artificial boundary between the browser and server, allowing engineers to code both. Built almost twice as fast with fewer people Written in 33% fewer lines of code Constructed with 40% fewer files Double the requests per second vs. the Java application. 35% decrease in the average response time for the same page. A common pro Java response is an argument like clearly these people don't know how to program Java. Or rewriting an application usually makes it faster. Or the benchmark is faulty. And so on. Consider it noted. These are all potential factors. Baron Schwartz from VividCortex has a different tak
3 0.7043981 471 high scalability-2008-12-19-Gigaspaces curbs latency outliers with Java Real Time
Introduction: Today, most banks have migrated their internal software development from C/C++ to the Java language because of well-known advantages in development productivity (Java Platform), robustness & reliability (Garbage Collector) and platform independence (Java Bytecode). They may even have gotten better throughput performance through the use of standard architectures and application servers (Java Enterprise Edition). Among the few banking applications that have not been able to benefit yet from the Java revolution, you find the latency-critical applications connected to the trading floor. Why? Because of the unpredictable pauses introduced by the garbage collector which result in significant jitter (variance of execution time). In this post Frederic Pariente Engineering Manager at Sun Microsystems posted a summary of a case study on how the use of Sun Real Time JVM and GigaSpaces was used in the context of of a customer proof-of-concept this summer to ensure guaranteed latency per m
4 0.67998195 459 high scalability-2008-12-03-Java World Interview on Scalability and Other Java Scalability Secrets
Introduction: OK, this interview is with me on Java scalability issues. I sound like a bigger idiot than I would like, but I suppose it could have been worse. The Java World folks were very nice and did a good job, so there’s no blame on them :-) The interview went an interesting direction, but there’s more I’d like add and I will do so here. Two major rules regarding Java and scalability have popped out at me: Java – It’s the platform stupid . Java the language isn’t the big win. What is the big win is the ecosystem building up around the JVM, libraries, and toolsets. Java – It’s the community stupid . A lot of creativity is being expended on leveraging the Java platform to meet scalability challenges. The amazing community that has built up around Java is pushing Java to the next level in almost every direction imaginable. The fecundity of the Java ecosystem can most readily be seen with the efforts to tame our multi-core future. There’s a multi-core crisis going in case you haven’t
5 0.65674603 550 high scalability-2009-03-30-Ebay history and architecture
Introduction: Ebay [1] Starts in 1995, initial name AuctionWeb (V1) : - very simple architecture - based on perl - no database, for data persistence they used plain files Because of rapid growth they needed to improve their architecture and so V2 (clever name) was born: - replaced perl with C/C++ - started using a database in a master-slave configuration - C++ back-end - XSLT front-end Any request will lead to an XML file being created in C++ and the XLST processor will transform that into html. *pretty sophisticated architecture for the 90s, XLST was cutting-edge back then* That hold out pretty well for a while but in the late 90s ebay experienced an exponential growth. They started having some trouble with outages and needed improvements, so V3 was developed: - based on java - search engine still used C++ - proof that relational databases can scale (aggressive caching) - developed a messaging layer for making a lot of asyncronious calls, they a
6 0.65671867 364 high scalability-2008-08-14-Product: Terracotta - Open Source Network-Attached Memory
7 0.56516308 82 high scalability-2007-09-06-Why doesn't anyone use j2ee?
8 0.52339774 338 high scalability-2008-06-02-Total Cost of Ownership for different web development frameworks
9 0.4982821 1118 high scalability-2011-09-19-Big Iron Returns with BigMemory
10 0.48314396 653 high scalability-2009-07-08-Servers Component - How to choice and build perfect server
11 0.47974738 161 high scalability-2007-11-20-Product: SmartFrog a Distributed Configuration and Deployment Framework
12 0.47659519 320 high scalability-2008-05-17-DB2 Express-C
13 0.46382725 438 high scalability-2008-11-05-Managing application on the cloud using a JMX Fabric
14 0.46106762 993 high scalability-2011-02-22-Is Node.js Becoming a Part of the Stack? SimpleGeo Says Yes.
15 0.46008918 585 high scalability-2009-04-29-How to choice and build perfect server
16 0.45615366 434 high scalability-2008-10-30-Olio Web2.0 Toolkit - Evaluate Web Technologies and Tools
17 0.45569712 1551 high scalability-2013-11-20-How Twitter Improved JVM Performance by Reducing GC and Faster Memory Allocation
18 0.45101649 469 high scalability-2008-12-17-Scalability Strategies Primer: Database Sharding
19 0.45064929 346 high scalability-2008-06-28-ID generation schemes
20 0.4473469 575 high scalability-2009-04-21-Thread Pool Engine in MS CLR 4, and Work-Stealing scheduling algorithm
topicId topicWeight
[(2, 0.231), (37, 0.547)]
simIndex simValue blogId blogTitle
1 0.7639209 891 high scalability-2010-09-01-Scale-out vs Scale-up
Introduction: In this post I'll cover the difference between multi-core concurrency that is often referred to as Scale-Up and distributed computing that is often referred to as Scale-Out mode. more ..
2 0.70100421 1033 high scalability-2011-05-02-The Updated Big List of Articles on the Amazon Outage
Introduction: Since The Big List Of Articles On The Amazon Outage was published we've a had few updates that people might not have seen. Amazon of course released their Summary of the Amazon EC2 and Amazon RDS Service Disruption in the US East Region . Netlix shared their Lessons Learned from the AWS Outage as did Heroku ( How Heroku Survived the Amazon Outage ), Smug Mug ( How SmugMug survived the Amazonpocalypse ), and SimpleGeo ( How SimpleGeo Stayed Up During the AWS Downtime ). The curious thing from my perspective is the general lack of response to Amazon's explanation. I expected more discussion. There's been almost none that I've seen. My guess is very few people understand what Amazon was talking about enough to comment whereas almost everyone feels qualified to talk about the event itself. Lesson for crisis handlers : deep dive post-mortems that are timely, long, honestish, and highly technical are the most effective means of staunching the downward spiral of media attention.
3 0.6273185 1029 high scalability-2011-04-25-The Big List of Articles on the Amazon Outage
Introduction: Please see The Updated Big List Of Articles On The Amazon Outage for a new improved list. So many great articles have been written on the Amazon Outage. Some aim at being helpful, some chastise developers for being so stupid, some chastise Amazon for being so incompetent, some talk about the pain they and their companies have experienced, and some even predict the downfall of the cloud. Still others say we have seen a sea change in future of the cloud, a prediction that's hard to disagree with, though the shape of the change remains...cloudy. I'll try to keep this list update as more information comes out. There will be a lot for developers to consider going forward. If there's a resource you think should be added, just let me know. Amazon's Explanation of What Happened Summary of the Amazon EC2 and Amazon RDS Service Disruption in the US East Region Hackers News thread on AWS Service Disruption Post Mortem Quite Funny Commentary on the Summary Experiences f
same-blog 4 0.59830141 113 high scalability-2007-10-07-Paper: Architecture of a Highly Scalable NIO-Based Server
Introduction: The article describes the basic architecture of a connection-oriented NIO-based java server. It takes a look at a preferred threading model, Java Non-blocking I/O and discusses the basic components of such a server.
5 0.52077854 311 high scalability-2008-04-29-Strategy: Sample to Reduce Data Set
Introduction: Update: Arjen links to video Supporting Scalable Online Statistical Processing which shows "rather than doing complete aggregates, use statistical sampling to provide a reasonable estimate (unbiased guess) of the result." When you have a lot of data, sampling allows you to draw conclusions from a much smaller amount of data. That's why sampling is a scalability solution. If you don't have to process all your data to get the information you need then you've made the problem smaller and you'll need fewer resources and you'll get more timely results. Sampling is not useful when you need a complete list that matches a specific criteria. If you need to know the exact set of people who bought a car in the last week then sampling won't help. But, if you want to know many people bought a car then you could take a sample and then create estimate of the full data-set. The difference is you won't really know the exact car count. You'll have a confidence interval saying how confident
6 0.51922691 103 high scalability-2007-09-28-Kosmos File System (KFS) is a New High End Google File System Option
7 0.51565224 1379 high scalability-2012-12-31-Designing for Resiliency will be so 2013
8 0.50922173 1133 high scalability-2011-10-27-Strategy: Survive a Comet Strike in the East With Reserved Instances in the West
9 0.50315773 316 high scalability-2008-05-05-Put the web server on a diet and increase scalability
10 0.4937067 965 high scalability-2010-12-29-Pinboard.in Architecture - Pay to Play to Keep a System Small
11 0.48190027 1415 high scalability-2013-03-04-7 Life Saving Scalability Defenses Against Load Monster Attacks
12 0.44836885 314 high scalability-2008-05-03-Product: nginx
13 0.4221493 620 high scalability-2009-06-05-SSL RPC API Scalability
14 0.40937746 329 high scalability-2008-05-27-Secure Remote Administration for Large-Scale Networks
15 0.39274922 1366 high scalability-2012-12-03-Resiliency is the New Normal - A Deep Look at What It Means and How to Build It
16 0.38995212 1418 high scalability-2013-03-06-Low Level Scalability Solutions - The Aggregation Collection
17 0.3890627 56 high scalability-2007-08-03-Running Hadoop MapReduce on Amazon EC2 and Amazon S3
18 0.3890627 565 high scalability-2009-04-13-Benchmark for keeping data in browser in AJAX projects
19 0.38886899 436 high scalability-2008-11-02-Strategy: How to Manage Sessions Using Memcached
20 0.38862139 223 high scalability-2008-01-25-Google: Introduction to Distributed System Design