"Chris is one of the industry's most important thinkers on database design . . . I would strongly recommend this book to readers trying to get past the buzzwords and focus on what really makes a difference in achieving high-performance distributed systems." --David Stodder Editor-in-Chief, Database Programming & Design
Performance is not simply a matter of tuning the code or the computing environment--it starts with designing performance into the application from the outset, and spans all phases of the system life cycle. Drawing on his 25 years of experience, Chris Loosley explains the principles of software performance engineering and applies them to all facets of distributed systems architecture and design. Along the way, he summarizes his conclusions in over 250 useful, easily referenced guidelines. And he covers all the key topics, with chapters on Middleware, Architecture, Design, Tools, Databases, Replication, Warehousing, and Transaction Monitors.
Loosley's conclusions about the architecture and design of enterprise systems challenge many current middleware trends. Applying the performance principles, Loosley explains why the key to creating truly scalable distributed systems is to decompose complex business applications into multitransaction workflows, and to use asynchronous data replication, parallel processing, and batching techniques.
Sid Adelman, Sid Adelman and Associates
Nagraj Alur, DataBase Associates International
Charles Brett, C3B Consulting
Tom Cushing, Advanced Computer Services
Mike Ferguson, DataBase Associates International
John Kneiling, DataBase Associates International
David Linthicum, Ernst & Young
Alejandro Mimo, DataBase Associates International
Neal Nelson, Neal Nelson and Associates
George Peters, MCI Systemhouse
Colin White, DataBase Associates International
Paul Winsberg, DataBase Associates International
49 pages matching query in this book
Results 1-3 of 49
What people are saying - Write a review
While the information would appear to be out of date, the concepts presented are as fresh as ever.
I use this book and refer my internal clients to the concepts at least monthly. This is high for an internal conclustant who generally works with the same 100-300 people yearly.
I get called in when the applicaiton is not passing the Performance Test time frame. Rather late in the design, but better than after it goes live. I have had much better success at introducing these concepts when we are consulted during the design review time just before it is going to the Off-Shore team for implementation of the code against that design. Then we still have room to change some basic usage of the system.
It seems people still think that a service call is 'cheap' and that it does not matter how many of them are made during a 'unit-of-work'. Chris' concept on Efficieny Principle and Trade-Off Principle come into play with those concerns.
Still a high value read for the concepts.
A Vision of Unlimited Scalability
45 other sections not shown