InfoQ Homepage Performance & Scalability Content on InfoQ
-
Abstractions at Scale–Our Experiences at Twitter
Marius Eriksen considers that leaky abstractions lead to scalability issues, while those providing narrow access to explicit resources - map-reduce, shared-nothing web apps, big table - scale better.
-
Development at the Speed and Scale of Google
Ashish Kumar on how Google keeps the source code of over 2000 projects in a single code trunk containing 100s of M of code lines, with more than 5,000 developers accessing the same repository.
-
The Evolution of the Flickr Architecture
Mikhail Panchenko discusses how Flickr’s code base developed over the years and the scalability problems that started to appear, presenting the the improvements and pros/cons of technologies used.
-
Scaling Australia's Most Popular Online News Sites with Ehcache
A real-world experience of implementing Ehcache at Australia's most visited online news site. How to deal with high traffic, concurrency, and how to implement linear scalability.
-
Fast Enough
Cliff Moon explains how to make Erlang programs faster by writing performance critical sections of the code in C using NIFs and by integrating libraries using the linked-in driver interface.
-
Performance Testing at the Edge
Alois Reitbauer shows how to do performance testing during development, testing, and production by starting early in the development phase, breaking the test into pieces, and testing continuously.
-
Neo4j: NOSQL and the Benefits of Graph Databases
Emil Eifrem overviews the trends leading to NOSQL, and four emerging NOSQL solutions. He also explains the internals of a graph database and an example of using Neo4j – a graph DB - in production.
-
Social Networks: Getting Distributed Web Services Done with NoSQL
Lars George and Fabrizio Schmidt present Germany’s largest social networks, Schuelervz, Studivz and Meinvz, the initial architecture, why it didn’t work and how they solved it with a NoSQL solution.
-
Embracing Concurrency At Scale
Justin Sheehy explains the principles behind concurrent distributed systems: no global state, no ACID but rather BASE, no RPC but protocols over APIs, prepare for failure, degradation, measurement.
-
Project Voldemort at Gilt Groupe: When Failure Isn't an Option
Geir Magnusson explains why Gilt Groupe is using Project Voldemort to scale out their e-commerce transactional system, what are the benefits and what is the current architecture after ditching SQL.
-
Scaling Your Cache & Caching at Scale
Alex Miller presents typical difficulties encountered when setting up a cache, plus available choices for designing a distributed caching architecture, and ways to test a cache for performance.
-
The Wizardry of Scaling
Oren Eini presents several architectural concepts – divide and conquer, background evaluation, one way messaging, the single responsibility principle - helpful to build highly scalable systems.