04 Oct
Posted by Coder as Architecture, Availability, Best practices, Java, Performance, Reliability, Scalability, Web Services, map reduce
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)
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Aug | Nov » | |||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | 31 | ||||
RSS feed for comments on this post · TrackBack URI
Leave a reply