Architecting Enterprise Solutions
and over one million other books are available for Amazon Kindle .
Learn more
| |||||||||||||||
 Trade In this Item for up to £6.60
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Architecting Enterprise Solutions: Patterns for High-capability Internet-based Systems for an Amazon.co.uk gift card of up to £6.60, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Author
Product Description
Product Description
- A practical, nuts–and–bolts guide to architectural solutions that describes step–by–step how to design robustness and flexibility into an Internet–based system
- Based on real–world problems and systems, and illustrated with a running case study
- Enables 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 demands
- Platform and vendor independence will empower architects to challenge product–dictated limitations
From the Back Cover
Companies increasingly rely on systems that are secure, flexible and available 24x7. They are often developed in a very short time frame with changing requirements and increasing levels of complexity. Despite this, they must still display acceptable levels of performance, availability, scalability, security and a variety of other non–functional characteristics. These requirements need to be addressed in every part of the system including hardware, software, network topology and system configuration.
Architecting Enterprise Solutions is based on real world problems and systems. It takes a practical approach to architectural solutions giving step–by–step advice on how to design high performance, controllable and flexible systems. Design patterns provide a platform–independent way to show tried and tested solutions to common pitfalls and problems encountered when developing high–capability systems. The running case study illustrates the evolution of a system as it grows in functionality and capability, and each chapter closes with a new evolutionary variant of the overall system, illustrating its improved cap abilities.
Whether you are looking to gain insight into architectural problems and solutions or in need of practical help in day–to–day system construction, Paul Dyson and Andy Longshaw provide a practical and solution–focused aid to architecting enterprise solutions.
Inside This Book
(Learn More)
First Sentence
Many of today's 'enterprise solutions' - systems that execute the fundamental business functions of an organization - are being implemented using Internet technology. Read the first page
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Many of today's 'enterprise solutions' - systems that execute the fundamental business functions of an organization - are being implemented using Internet technology. Read the first page
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
Customer Reviews
There are no customer reviews yet on Amazon.co.uk.
5 star
4 star
3 star
2 star
1 star
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
6 reviews
6 of 7 people found the following review helpful
Know-how for architecting Internet-based software systems
14 April 2006
Format:Hardcover
Non-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.
"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.
2 of 2 people found the following review helpful
Real-world experiences
15 Oct 2009
Format:Hardcover
That author focuses on that the fact that system architecture is driven by non-functional requirements. This is a critical fact that is missed by many other books on architecture.
1 of 1 people found the following review helpful
For the Titans, not to everyones
16 Sep 2008
Format:Hardcover|Amazon Verified Purchase
C. Arnold made a very realistic review about this book. In past years I've 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, doesn't 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.
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.
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
