high_scalability high_scalability-2012 high_scalability-2012-1258 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Benjamin Erb ( @b_erb ) from Ulm University recently published his diploma thesis on "Concurrent Programming for Scalable Web Architectures" . The thesis provides a comprehensive survey on different concepts and techniques of concurrency inside web architectures, including web servers, application logic and storage backends. It incorporates research publications, hands-on reports and also regards popular programming languages, frameworks and databases. Abstract: Web architectures are an important asset for various large-scale web applications, such as social networks or e-commerce sites. Being able to handle huge numbers of users concurrently is essential, thus scalability is one of the most important features of these architectures. Multi-core processors, highly distributed backend architectures and new web technologies force us to reconsider approaches for concurrent programming in order to implement web applications and fulfil scalability demands. While focusing on dif
sentIndex sentText sentNum sentScore
1 Benjamin Erb ( @b_erb ) from Ulm University recently published his diploma thesis on "Concurrent Programming for Scalable Web Architectures" . [sent-1, score-0.215]
2 The thesis provides a comprehensive survey on different concepts and techniques of concurrency inside web architectures, including web servers, application logic and storage backends. [sent-2, score-1.866]
3 It incorporates research publications, hands-on reports and also regards popular programming languages, frameworks and databases. [sent-3, score-0.333]
4 Abstract: Web architectures are an important asset for various large-scale web applications, such as social networks or e-commerce sites. [sent-4, score-0.645]
5 Being able to handle huge numbers of users concurrently is essential, thus scalability is one of the most important features of these architectures. [sent-5, score-0.072]
6 Multi-core processors, highly distributed backend architectures and new web technologies force us to reconsider approaches for concurrent programming in order to implement web applications and fulfil scalability demands. [sent-6, score-1.621]
7 While focusing on different stages of scalable web architectures, we provide a survey of competing concurrency approaches and point to their adequate usages. [sent-7, score-1.371]
wordName wordTfidf (topN-words)
[('concurrency', 0.42), ('concepts', 0.308), ('architectures', 0.301), ('web', 0.272), ('scalabale', 0.245), ('concurrent', 0.215), ('thesis', 0.156), ('survey', 0.154), ('internals', 0.152), ('programming', 0.147), ('approaches', 0.144), ('threads', 0.13), ('fulfil', 0.111), ('scalable', 0.101), ('transactional', 0.098), ('trends', 0.098), ('regards', 0.093), ('fundamentals', 0.093), ('incorporates', 0.093), ('publications', 0.091), ('languages', 0.089), ('distributed', 0.085), ('backends', 0.083), ('wide', 0.081), ('adequate', 0.079), ('benjamin', 0.078), ('logic', 0.077), ('multithreaded', 0.077), ('quest', 0.075), ('applications', 0.074), ('contents', 0.073), ('storage', 0.073), ('asset', 0.072), ('concurrently', 0.072), ('picking', 0.07), ('comprehensive', 0.069), ('selecting', 0.069), ('focusing', 0.069), ('upcoming', 0.068), ('scope', 0.068), ('stages', 0.066), ('competing', 0.066), ('actors', 0.066), ('including', 0.065), ('university', 0.063), ('road', 0.06), ('hybrid', 0.06), ('conclusion', 0.06), ('server', 0.059), ('published', 0.059)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999988 1258 high scalability-2012-06-05-Thesis: Concurrent Programming for Scalable Web Architectures
Introduction: Benjamin Erb ( @b_erb ) from Ulm University recently published his diploma thesis on "Concurrent Programming for Scalable Web Architectures" . The thesis provides a comprehensive survey on different concepts and techniques of concurrency inside web architectures, including web servers, application logic and storage backends. It incorporates research publications, hands-on reports and also regards popular programming languages, frameworks and databases. Abstract: Web architectures are an important asset for various large-scale web applications, such as social networks or e-commerce sites. Being able to handle huge numbers of users concurrently is essential, thus scalability is one of the most important features of these architectures. Multi-core processors, highly distributed backend architectures and new web technologies force us to reconsider approaches for concurrent programming in order to implement web applications and fulfil scalability demands. While focusing on dif
2 0.16650487 539 high scalability-2009-03-16-Books: Web 2.0 Architectures and Cloud Application Architectures
Introduction: I am excited about the upcoming release of two books on Web 2.0 and Cloud Application Architectures by O'Reilly. Web 2.0 Architectures (estimated release in May 2009) What entrepreneurs and information architects need to know Using several high-profile Web 2.0 companies as examples, authors Duane Nickull, Dion Hinchcliffe, and James Governor have distilled the core patterns of Web 2.0 coupled with an abstract model and reference architecture. The result is a base of knowledge that developers, business people, futurists, and entrepreneurs can understand and use as a source of ideas and inspiration. Featured architectures include Google, Flickr, BitTorrent, MySpace, Facebook, and Wikipedia. Cloud Application Architectures (estimated release in April 2009) Building Applications and Infrastructure in the Cloud This book by George Reese offers tested techniques for creating web applications on cloud computing infrastructures and for migrating existing system
3 0.15200864 772 high scalability-2010-02-05-High Availability Principle : Concurrency Control
Introduction: One important high availability principle is concurrency control. The idea is to allow only that much traffic through to your system which your system can handle successfully. For example: if your system is certified to handle a concurrency of 100 then the 101st request should either timeout, be asked to try later or wait until one of the previous 100 requests finish. The 101st request should not be allowed to negatively impact the experience of the other 100 users. Only the 101st request should be impacted. Read more here...
4 0.14375421 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
5 0.13732232 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
6 0.13509096 1446 high scalability-2013-04-25-Paper: Making reliable distributed systems in the presence of software errors
8 0.11300273 705 high scalability-2009-09-16-Paper: A practical scalable distributed B-tree
9 0.11262404 236 high scalability-2008-02-03-Ideas on how to scale a shared inventory database???
10 0.11120144 427 high scalability-2008-10-22-Server load balancing architectures, Part 2: Application-level load balancing
11 0.1109479 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
12 0.11040417 1299 high scalability-2012-08-06-Paper: High-Performance Concurrency Control Mechanisms for Main-Memory Databases
13 0.10813408 1634 high scalability-2014-04-18-Stuff The Internet Says On Scalability For April 18th, 2014
14 0.10555741 1534 high scalability-2013-10-18-Stuff The Internet Says On Scalability For October 18th, 2013
15 0.10554464 1276 high scalability-2012-07-04-Top Features of a Scalable Database
16 0.10479054 14 high scalability-2007-07-15-Web Analytics: An Hour a Day
17 0.10196265 891 high scalability-2010-09-01-Scale-out vs Scale-up
18 0.099938147 459 high scalability-2008-12-03-Java World Interview on Scalability and Other Java Scalability Secrets
topicId topicWeight
[(0, 0.168), (1, 0.018), (2, 0.057), (3, 0.042), (4, 0.01), (5, 0.041), (6, -0.022), (7, -0.048), (8, -0.113), (9, 0.104), (10, -0.028), (11, 0.015), (12, -0.045), (13, -0.025), (14, -0.064), (15, -0.083), (16, 0.041), (17, 0.015), (18, 0.072), (19, -0.049), (20, 0.038), (21, 0.036), (22, -0.08), (23, -0.012), (24, 0.034), (25, -0.125), (26, -0.039), (27, -0.052), (28, 0.091), (29, -0.005), (30, 0.05), (31, 0.017), (32, 0.04), (33, -0.065), (34, -0.078), (35, -0.073), (36, -0.035), (37, 0.002), (38, 0.048), (39, -0.025), (40, 0.014), (41, -0.008), (42, -0.052), (43, -0.051), (44, -0.033), (45, 0.064), (46, -0.048), (47, -0.017), (48, 0.036), (49, -0.023)]
simIndex simValue blogId blogTitle
same-blog 1 0.9585619 1258 high scalability-2012-06-05-Thesis: Concurrent Programming for Scalable Web Architectures
Introduction: Benjamin Erb ( @b_erb ) from Ulm University recently published his diploma thesis on "Concurrent Programming for Scalable Web Architectures" . The thesis provides a comprehensive survey on different concepts and techniques of concurrency inside web architectures, including web servers, application logic and storage backends. It incorporates research publications, hands-on reports and also regards popular programming languages, frameworks and databases. Abstract: Web architectures are an important asset for various large-scale web applications, such as social networks or e-commerce sites. Being able to handle huge numbers of users concurrently is essential, thus scalability is one of the most important features of these architectures. Multi-core processors, highly distributed backend architectures and new web technologies force us to reconsider approaches for concurrent programming in order to implement web applications and fulfil scalability demands. While focusing on dif
2 0.68794221 539 high scalability-2009-03-16-Books: Web 2.0 Architectures and Cloud Application Architectures
Introduction: I am excited about the upcoming release of two books on Web 2.0 and Cloud Application Architectures by O'Reilly. Web 2.0 Architectures (estimated release in May 2009) What entrepreneurs and information architects need to know Using several high-profile Web 2.0 companies as examples, authors Duane Nickull, Dion Hinchcliffe, and James Governor have distilled the core patterns of Web 2.0 coupled with an abstract model and reference architecture. The result is a base of knowledge that developers, business people, futurists, and entrepreneurs can understand and use as a source of ideas and inspiration. Featured architectures include Google, Flickr, BitTorrent, MySpace, Facebook, and Wikipedia. Cloud Application Architectures (estimated release in April 2009) Building Applications and Infrastructure in the Cloud This book by George Reese offers tested techniques for creating web applications on cloud computing infrastructures and for migrating existing system
3 0.66776049 122 high scalability-2007-10-14-Product: The Spread Toolkit
Introduction: Complex applications coordinating work across a lot of machines often need a highly performing fault tolerant message layer. Though a blast to write, it's probably a better use of your time to use an off the shelf solution. And that's where Spread comes in. Flickr, for example, uses Spread to create real-time event feeds from their web server logs. What exactly is Spread? From the Spread website: Spread is an open source toolkit that provides a high performance messaging service that is resilient to faults across local and wide area networks. Spread functions as a unified message bus for distributed applications, and provides highly tuned application-level multicast, group communication, and point to point support. Spread services range from reliable messaging to fully ordered messages with delivery guarantees. Spread can be used in many distributed applications that require high reliability, high performance, and robust communication among various subsets of members. The
4 0.63718653 1446 high scalability-2013-04-25-Paper: Making reliable distributed systems in the presence of software errors
Introduction: Joe Armstrong is a co-inventor of Erlang and general all around renaissance software tinkerer as shown by his excellent work on writing a C Compiler and his voluminous work on GitHub . Given the success of Erlang it's probably no surprise that he wrote his thesis on the ground breaking ideas behind Erlang: Making reliable distributed systems in the presence of software errors . Even if you have yet to join the cult of Erlang the principles behind Erlang are universal and well worth exploring for your own designs. Highly recommended. Introduction: How can we program systems which behave in a reasonable manner in the presence of software errors? This is the central question that I hope to answer in this thesis. Large systems will probably always be delivered containing a number of errors in the software, nevertheless such systems are expected to behave in a reasonable manner. To make a reliable system from faulty components places certain requirements on the system. Th
Introduction: How do you layer a programmable Internet of smart things on top of the web? That's the question addressed by Dominique Guinard  in his ambitious dissertation: A Web of Things Application Architecture - Integrating the Real-World  ( slides ). With the continued siloing of content, perhaps we can keep our things open and talking to each other? In the architecture things are modeled using REST, they will be findable via search, they will be social via a social access controller, and they will be mashupable. Here's great graphical overview of the entire system:  Abstract: A central concern in the area of pervasive computing has been the integration of digital artifactsts with the physical world and vice-versa. Recent developments in the fi eld of embedded devices have led to smart things increasingly populating our daily life. We de fine smart things as digitally enhanced physical objectsts and devices that have communication capabilities. Application domains are for i
6 0.63145953 569 high scalability-2009-04-14-Scalability resources
7 0.62896204 604 high scalability-2009-05-20-Paper: Flux: An Adaptive Partitioning Operator for Continuous Query Systems
8 0.62621337 51 high scalability-2007-07-31-Book: Scalable Internet Architectures
9 0.61879808 10 high scalability-2007-07-15-Book: Building Scalable Web Sites
10 0.61848068 1087 high scalability-2011-07-26-Web 2.0 Killed the Middleware Star
11 0.61309683 1299 high scalability-2012-08-06-Paper: High-Performance Concurrency Control Mechanisms for Main-Memory Databases
13 0.60764802 1127 high scalability-2011-09-28-Pursue robust indefinite scalability with the Movable Feast Machine
14 0.60479832 400 high scalability-2008-10-01-The Pattern Bible for Distributed Computing
15 0.59867972 434 high scalability-2008-10-30-Olio Web2.0 Toolkit - Evaluate Web Technologies and Tools
16 0.59748149 695 high scalability-2009-09-06-Some Hot Links
17 0.59654486 709 high scalability-2009-09-19-Space Based Programming in .NET
18 0.5943563 346 high scalability-2008-06-28-ID generation schemes
19 0.5780108 877 high scalability-2010-08-12-Designing Web Applications for Scalability
20 0.57373691 402 high scalability-2008-10-05-Paper: Scalability Design Patterns
topicId topicWeight
[(1, 0.138), (2, 0.269), (10, 0.037), (40, 0.039), (49, 0.16), (61, 0.095), (79, 0.078), (85, 0.046), (94, 0.016)]
simIndex simValue blogId blogTitle
1 0.96714801 400 high scalability-2008-10-01-The Pattern Bible for Distributed Computing
Introduction: Software design patterns are an emerging tool for guiding and documenting system design. Patterns usually describe software abstractions used by advanced designers and programmers in their software. Patterns can provide guidance for designing highly scalable distributed systems. Let's see how! Patterns are in essence solutions to problems. Most of them are expressed in a format called Alexandrian form which draws on constructs used by Christopher Alexander. There are variants but most look like this: The pattern name The problem the pattern is trying to solve Context Solution Examples Design rationale: This tells where the pattern came from, why it works, and why experts use it Patterns rarely stand alone. Each pattern works on a context, and transforms the system in that context to produce a new system in a new context. New problems arise in the new system and context, and the next ‘‘layer’’ of patterns can be applied. A pattern language is a structured col
2 0.96528316 737 high scalability-2009-11-05-A Yes for a NoSQL Taxonomy
Introduction: NorthScale's Steven Yen in his highly entertaining NoSQL is a Horseless Carriage presentation has come up with a NoSQL taxonomy that thankfully focuses a little more on what NoSQL is, than what it isn't : key‐value‐cache memcached, repcached, coherence, infinispan, eXtreme scale, jboss cache, velocity, terracoqa key‐value‐store keyspace, flare, schema‐free, RAMCloud eventually‐consistent key‐value‐store dynamo, voldemort, Dynomite, SubRecord, Mo8onDb, Dovetaildb ordered‐key‐value‐store tokyo tyrant, lightcloud, NMDB, luxio, memcachedb, actord data‐structures server redis tuple‐store gigaspaces, coord, apache river object database ZopeDB, db4o, Shoal document store CouchDB, Mongo, Jackrabbit, XML Databases, ThruDB, CloudKit, Perservere, Riak Basho, Scalaris wide columnar store BigTable, Hbase, Cassandra, Hypertable, KAI, OpenNeptune, Qbase, KDI "Who will win?"
3 0.94564152 1311 high scalability-2012-08-24-Stuff The Internet Says On Scalability For August 24, 2012
Introduction: It's HighScalability Time: 500 TB/day: Facebook data Quotable Quotes: Tumblr mobocracy : This is what migrating a billion cache objects into a new cache pool looks like #hoti it is possible to build all to all wdm networks where there is a wavelength per core. A Generation Lost in the Bazaar . The problem is Cathedrals are multi-generation projects, built by master craftsman, using an empirical process, not engineering principles. There is no complete specification, it's iterative and adaptive. How Bazaar. Here's a unique look at how the new Digg 4 structured their architecture and development processes to scale down to 14 engineers from a high of 40 engineers for the old Digg. As the team shrunk very few new unit tests were written and the system tests were dumped. Using Thrift between components helped coordinate the team. A dark rollout mechanism allowed them to rollout and test features on a subset of users. Development team used
4 0.94242549 735 high scalability-2009-11-01-Squeeze more performance from Parallelism
Introduction: In many posts, such as: The Future of the Parallelism and its Challenges I mentioned that synchronization the access to the shared resource is the major challenge to write parallel code. The synchronization and coordination take long time from the overall execution time, which reduce the benefits of the parallelism; the synchronization and coordination also reduce the scalability. There are many forms of synchronization and coordination, such as: Create Task object in frameworks such as: Microsoft TPL, Intel TDD, and Parallel Runtime Library. Create and enqueue task objects require synchronization that it’s takes long time especially if we create it into recursive work such as: Quick Sort algorithm. Synchronization the access to shared data. But there are a few techniques to avoid these issues, such as: Shared-Nothing, Actor Model, and Hyper Object (A.K.A. Combinable Object). Simply if we reduce the shared data by re-architect our code this will gives us a huge benefits
5 0.92725438 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
6 0.92243093 183 high scalability-2007-12-12-Report from OpenSocial Meetup at Google
7 0.92033893 1359 high scalability-2012-11-15-Gone Fishin': Justin.Tv's Live Video Broadcasting Architecture
8 0.91861469 823 high scalability-2010-05-05-How will memristors change everything?
9 0.91715831 796 high scalability-2010-03-16-Justin.tv's Live Video Broadcasting Architecture
10 0.91680634 568 high scalability-2009-04-14-Designing a Scalable Twitter
11 0.91471612 843 high scalability-2010-06-16-WTF is Elastic Data Grid? (By Example)
12 0.91413528 1114 high scalability-2011-09-13-Must see: 5 Steps to Scaling MongoDB (Or Any DB) in 8 Minutes
14 0.91114521 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
same-blog 15 0.90375197 1258 high scalability-2012-06-05-Thesis: Concurrent Programming for Scalable Web Architectures
16 0.89892101 1519 high scalability-2013-09-18-If You're Programming a Cell Phone Like a Server You're Doing it Wrong
17 0.8968274 399 high scalability-2008-10-01-Joyent - Cloud Computing Built on Accelerators
18 0.89483219 927 high scalability-2010-10-26-Marrying memcached and NoSQL
19 0.89342201 1507 high scalability-2013-08-26-Reddit: Lessons Learned from Mistakes Made Scaling to 1 Billion Pageviews a Month
20 0.89232385 821 high scalability-2010-05-03-MocoSpace Architecture - 3 Billion Mobile Page Views a Month