Advances in Distributed Computing and Middleware Ser.: Distributed Systems for System Architects by Luís Rodrigues and Paulo Veríssimo (2001, Hardcover)

ZUBER (264780)
97.8% positive feedback
Price:
US $122.95
ApproximatelyRM 522.02
+ $20.95 shipping
Estimated delivery Fri, 11 Jul - Thu, 24 Jul
Returns:
30 days return. Buyer pays for return shipping. If you use an eBay shipping label, it will be deducted from your refund amount.
Condition:
Good

About this product

Product Identifiers

PublisherSpringer
ISBN-100792372662
ISBN-139780792372660
eBay Product ID (ePID)1834528

Product Key Features

Number of PagesXxii, 625 Pages
Publication NameDistributed Systems for System Architects
LanguageEnglish
SubjectSystems Architecture / General, Systems Architecture / Distributed Systems & Computing, Computer Science
Publication Year2001
TypeTextbook
Subject AreaComputers
AuthorLuís Rodrigues, Paulo Veríssimo
SeriesAdvances in Distributed Computing and Middleware Ser.
FormatHardcover

Dimensions

Item Weight84 Oz
Item Length9.3 in
Item Width6.1 in

Additional Product Features

Intended AudienceScholarly & Professional
LCCN00-052178
Dewey Edition21
Series Volume Number1
Number of Volumes1 vol.
IllustratedYes
Dewey Decimal005/.36
Table Of ContentI Distribution.- 1. Distributed Systems Foundations.- 2. Distributed System Paradigms.- 3. Models Of Distributed Computing.- 4. Distributed Systems and Platforms.- 5. Case Study: VP'63.- II Fault Tolerance.- 6. Fault-Tolerant Systems Foundations.- 7. Paradigms for Distributed Fault Tolerance.- 8. Models of Distributed Fault-Tolerant Computing.- 9. Dependable Systems and Platforms.- 10. Case Study: VP'63.- III Real-Time.- 11. Real-Time Systems Foundations.- 12. Paradigms For Real-Time.- 13. Models Of Distributed Real-Time Computing.- 14. Distributed Real-Time Systems and Platforms.- 15. Case Study: VP'63.- IV Security.- 16. Fundamental Security Concepts.- 17. Security Paradigms.- 18. Models of Distributed Secure Computing.- 19. Secure Systems and Platforms.- 20. Case Study: VP'63.- V Management.- 21. Fundamental Concepts of Management.- 22. Paradigms for Distributed Systems Management.- 23. Models of Network and Distributed Systems Management.- 24. Management Systems and Platforms.- 25. Case Study: VP'63.- References.
SynopsisThe primary audience for this book are advanced undergraduate students and graduate students. Computer architecture, as it happened in other fields such as electronics, evolved from the small to the large, that is, it left the realm of low-level hardware constructs, and gained new dimensions, as distributed systems became the keyword for system implementation. As such, the system architect, today, assembles pieces of hardware that are at least as large as a computer or a network router or a LAN hub, and assigns pieces of software that are self-contained, such as client or server programs, Java applets or pro­ tocol modules, to those hardware components. The freedom she/he now has, is tremendously challenging. The problems alas, have increased too. What was before mastered and tested carefully before a fully-fledged mainframe or a closely-coupled computer cluster came out on the market, is today left to the responsibility of computer engineers and scientists invested in the role of system architects, who fulfil this role on behalf of software vendors and in­ tegrators, add-value system developers, R&D institutes, and final users. As system complexity, size and diversity grow, so increases the probability of in­ consistency, unreliability, non responsiveness and insecurity, not to mention the management overhead. What System Architects Need to Know The insight such an architect must have includes but goes well beyond, the functional properties of distributed systems., The primary audience for this book are advanced undergraduate students and graduate students. Computer architecture, as it happened in other fields such as electronics, evolved from the small to the large, that is, it left the realm of low-level hardware constructs, and gained new dimensions, as distributed systems became the keyword for system implementation. As such, the system architect, today, assembles pieces of hardware that are at least as large as a computer or a network router or a LAN hub, and assigns pieces of software that are self-contained, such as client or server programs, Java applets or pro- tocol modules, to those hardware components. The freedom she/he now has, is tremendously challenging. The problems alas, have increased too. What was before mastered and tested carefully before a fully-fledged mainframe or a closely-coupled computer cluster came out on the market, is today left to the responsibility of computer engineers and scientists invested in the role of system architects, who fulfil this role on behalf of software vendors and in- tegrators, add-value system developers, R&D institutes, and final users. As system complexity, size and diversity grow, so increases the probability of in- consistency, unreliability, non responsiveness and insecurity, not to mention the management overhead. What System Architects Need to Know The insight such an architect must have includes but goes well beyond, the functional properties of distributed systems.
LC Classification NumberTK7895.M5
No ratings or reviews yet
Be the first to write a review