Posted by Coder.
Oct
4
Posted by Coder.
Scalability chez Wall Street vs. chez Web2.0s
Nati Shalom’s Blog: Why most large-scale Web sites are not written in Java
…similar solutions for addressing the scalability challenges:
On the Data Tier we see the following:
1. Adding a caching layer to take advantage of memory resources availability and reduce I/O overhead
2. Moving from a database-centric approach to partitioning, aka shards
On the Business Logic Tier:
3. Adding parallelization semantics to the application tier (e.g., MapReduce)
4. Moving to scale-out application models to achieve linear scalability
5. Moving away from the classic two-phase commit and XA for transaction processing (See: Lessons from Pat Helland: Life Beyond Distributed Transactions)
There are 0 comments to this post.
Add Your Comment.
Previous Post
« Attributes of a Scalable (data intensive) Application Next Post
Improve Scalability With New Thread Pool APIs »
« Attributes of a Scalable (data intensive) Application Next Post
Improve Scalability With New Thread Pool APIs »