ePub Typography 34 by Type Directors Club in Arts-Photography

Review

1 of 1 people found the following review helpful. For the Titans; not to everyonesBy Eduardo XC. Arnold made a very realistic review about this book. In past years Ive been working a lot at on architecture subjects and read this book was like having a nice chat with someone on a high level than me where I careful pay attention on every single word said to me; doesnt matter if already have some knowledge about; it is nice to conciliate the knowledge.Could take decades to someone get the experience of the authors of this book. As I said to pinguinu:"Even if they talk something about JAVA; I could identify all the things to work with .net. In the end it is a platform independent subject and such things stays forever on the shelf.This book is for the Titans; not to everyone! It was a wonderful 3 weeks times until the end of the book."Thanks to C. Arnold; I bought this book because of his review.6 of 7 people found the following review helpful. Know-how for architecting Internet-based software systemsBy Fernando Berzal GalianoNon-functional requirements; i.e. the many software -ilities; are often neglected in the development of software systems. Even though they are a key factor in final user satisfaction and everybody acknowledges their importance; their prominence is usually downplayed. This book tries to fill this gap and it focuses on balancing the non-functional features of Internet-based software systems."Architecting Enterprise Solutions"; following the so-called patterns movement; is organized around a set of patterns; which are classified into four groups:1. Fundamental patterns describe the basic shape for Internet-based systems; why they tend to use application servers and why they recur to "specialist peripherals."2. Performance; availability; and scalability involve some kind of redundancy (e.g. the performance-related patterns involve tiers with redundant elements; load balancing; data replication; and effective resource management; such as pooling and caching).3. Control patterns deal with system manageability and security. Status reporting; monitoring; alerting; logging and dynamic configuration are key for manageability; while the proper use of demilitarized zones; firewalls; intrusion detection systems; encryption; and public key infrastructure are fundamental for security.4. Finally; evolution patterns address maintainability; flexibility; portability; and migration. Among other things; here you will find information on virtual platforms and staging environments.A final section describes how the patterns can be applied in practice; illustrating how the patterns trade-offs can lead to different system configurations.In summary; "Architecting Enterprise Solutions" collects the know-how of experienced system architects. It clearly shows how design decisions affect the non-functional characteristics of Internet-based systems and it does so without forgetting the cost implications of such decisions (something every architect on a tight budget will surely thank).Disclaimer: If you are just looking for solutions to the problems you face using a particular programming language; framework or platform; you should look elsewhere. If you would like to delve into the rationale behind key design decisions in Internet-based systems (beyond the use of particular technologies); this might be a good place to start.3 of 5 people found the following review helpful. Great overview of standard enterprise architecture.By BearsMy background is in enterprise application development/architecture; and I found this book to be a great introduction to the larger scope of system architecture. The patterns presented paint an easy to understand picture of what a highly capable Inter/intra- net system should look like.I found the level of detail to be great; as I was interested in an overview. If youre looking for implementation specifics; this would be a good starting point; but many of the platform-specific details would probably be found in other books.