This book will show you some of the best practices in designing an enterprise application that we have found invaluable in our own work. More and more our customers have asked for integration solutions over the last few years. With the introduction of SOAP and XML, we have found that we could use much of the same thinking when designing these applications as we used before. Of course, we have constantly evolved our thinking and refined our design patterns as new techniques have been introduced.
What This Book Does Not Cover
In this book, we will not discuss integration in and of itself. We will instead focus on a general design that can be implemented for many solutions, no matter what their purpose may be. We have tried to cover a broader spectrum than most books do. If there is one thing we have learned, it is that having the big picture is important. If a large project needs to be delivered on time and at the same time fulfill its expectations, developers and designers alike need to have a broad view of it. This obviously means we cannot be as thorough as we would like to be in many areas, but luckily other books are available for this. For example, the Sundblad and Sundblad books are valuable for their design patterns and modeling suggestions. Other books offer deep coverage of operating systems, databases, Web services, XML, and all those areas that are important to us. This book tries to bridge these boundaries so that you can build better applications for your customers or companies.
Building an enterprise application is not an easy task. If you do not design it properly from the beginning, the risk of failure will increase dramatically. Poor design might not be noticed at once, but with time, performance issues as well as extensibility issues are sure to emerge. To avoid this, IT architects and system designers need to have knowledge about what techniques are available and how these can be used.
What This Book Does Not Cover
In this book, we will not discuss integration in and of itself. We will instead focus on a general design that can be implemented for many solutions, no matter what their purpose may be. We have tried to cover a broader spectrum than most books do. If there is one thing we have learned, it is that having the big picture is important. If a large project needs to be delivered on time and at the same time fulfill its expectations, developers and designers alike need to have a broad view of it. This obviously means we cannot be as thorough as we would like to be in many areas, but luckily other books are available for this. For example, the Sundblad and Sundblad books are valuable for their design patterns and modeling suggestions. Other books offer deep coverage of operating systems, databases, Web services, XML, and all those areas that are important to us. This book tries to bridge these boundaries so that you can build better applications for your customers or companies.
Building an enterprise application is not an easy task. If you do not design it properly from the beginning, the risk of failure will increase dramatically. Poor design might not be noticed at once, but with time, performance issues as well as extensibility issues are sure to emerge. To avoid this, IT architects and system designers need to have knowledge about what techniques are available and how these can be used.
Hiç yorum yok:
Yorum Gönder