LEADER 05485nam 2200697Ia 450 001 9910449876703321 005 20200520144314.0 010 $a1-280-27034-9 010 $a9786610270347 010 $a0-470-85587-8 035 $a(CKB)1000000000023152 035 $a(EBL)194350 035 $a(OCoLC)57415230 035 $a(SSID)ssj0000105263 035 $a(PQKBManifestationID)11133636 035 $a(PQKBTitleCode)TC0000105263 035 $a(PQKBWorkID)10087921 035 $a(PQKB)10114675 035 $a(MiAaPQ)EBC194350 035 $a(Au-PeEL)EBL194350 035 $a(CaPaEBR)ebr10113999 035 $a(CaONFJC)MIL27034 035 $a(EXLCZ)991000000000023152 100 $a20040210d2004 uy 0 101 0 $aeng 135 $aurcn||||||||| 181 $ctxt 182 $cc 183 $acr 200 10$aArchitecting enterprise solutions$b[electronic resource] $epatterns for high-capability Internet-based systems /$fPaul Dyson, Andy Longshaw 210 $aHoboken, N.J. $cJohn Wiley & Sons$d2004 215 $a1 online resource (384 p.) 225 1 $aWiley Software Patterns Series 300 $aDescription based upon print version of record. 311 $a0-470-85612-2 320 $aIncludes bibliographical references and index. 327 $aContents; Acknowledgements; An All-Too-Common Story; In the beginning ...; In the middle ...; In the end ...; Chapter 1 Introduction; What this Book is About; What this Book is Not About; Why Write this Book?; Who Should Read this Book?; Architects; Developers; Project Managers; Students and Trainees; The Structure of the Book; Part 1; Part 2; Part 3; Reading the Book; PART 1 Architecture, Patterns and Internet Technology; Chapter 2 System Architecture; Architecture, Design and 'Goodness of Fit'; How does this Relate to System Architecture? 327 $aWhat are the Non-functional Characteristics we Care About?Balancing the Non-functional Characteristics; Defining System Architectures; Why do we Care About System Architecture?; Summary; Chapter 3 Internet Technology Systems; Types of Internet Technology System; Why do we Build Systems Using Internet Technology?; Building Blocks of Internet Technology Systems; Why is it Difficult?; Summary; Chapter 4 Architectural Patterns for Internet Technology Systems; Patterns, Languages and Internet Technology; Why do we use Patterns?; Patterns vs Principles; Organization of the Patterns 327 $aPresentation of the Patterns Navigating the Language; Summary; Chapter 5 The GlobalTech System; The Business Case; The System Overview; Summary; PART 2 The Patterns; Chapter 6 Fundamental Patterns; Getting the Shape Right; APPLICATION SERVER ARCHITECTURE; PERIPHERAL SPECIALIST ELEMENTS; What makes these Patterns Fundamental?; Summary; Chapter 7 System Performance Patterns; I Feel the Need, the Need for Speed; Principles; ACTIVE-REDUNDANT ELEMENTS; LOAD-BALANCED ELEMENTS; SESSION FAILOVER; DEDICATED WEB AND APPLICATION SERVERS; COMMON PERSISTENT STORE; Why Tiers are not a Catastrophe 327 $aDATA REPLICATION CONNECTION LIMITATION; RESOURCE POOLING; LOCAL CACHE; OFFLINE REPORTING; Other Patterns; Chapter 8 System Control Patterns; Dangerous (adj.): Speed Without Control; Terminology; CONTINUAL STATUS REPORTING; OPERATIONAL MONITORING AND ALERTING; 3-CATEGORY LOGGING; SYSTEM OVERVIEW; DYNAMICALLY-ADJUSTABLE CONFIGURATION; DEMILITARIZED ZONE; INFORMATION OBSCURITY; SECURE CHANNELS; Secure Sockets Layer and SSL Acceleration; KNOWN PARTNERS; Other Patterns; Chapter 9 System Evolution Patterns; Plus C?a Change; Principles; DYNAMICALLY-DISCOVERABLE ELEMENTS; EXPANDABLE HARDWARE 327 $aVIRTUAL PLATFORM SWAPPABLE STAGING ENVIRONMENT; SEPARATE SYSTEM-MANAGED DATA; Other Patterns; PART 3 Application of the Patterns; Chapter 10 GlobalTech Revisited; Reviewing the Architecture; Architecting for System Performance; Architecting for System Control; Architecting for System Evolution; Summary; Chapter 11 Applying the Patterns; Not Quite the Simplest System that Could Work; Which Patterns to Apply; A Process for Applying the Patterns?; Examples of Applying the Patterns; Summary; Chapter 12 Moving on from Here; Technology; Tool Support; Development Process 327 $aAn Evolutionary Approach to Architecture 330 $aA practical, nuts-and-bolts guide to architectural solutions that describes step-by-step how to design robustness and flexibility into an Internet-based systemBased on real-world problems and systems, and illustrated with a running case studyEnables software architects and project managers to ensure that nonfunctional requirements are met so that the system won't fall over, that it can be maintained and upgraded without being switched off, and that it can deal with security, scalability, and performance demandsPlatform and vendor independence will empower architects to 410 0$aWiley Software Patterns Series 606 $aInternet programming 606 $aComputer architecture 606 $aComputer systems 608 $aElectronic books. 615 0$aInternet programming. 615 0$aComputer architecture. 615 0$aComputer systems. 676 $a005.2/76 700 $aDyson$b Paul$0997014 701 $aLongshaw$b Andy$0997015 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910449876703321 996 $aArchitecting enterprise solutions$92286269 997 $aUNINA