SOA: Principles of Service Design
De Ccsl
SOA Principles of Service Design
Thomas Erl, Prentice Hall, 2007
This book describes SOA architecture as an environment designed in compliance with service-orientation design principles and composed by a combination of technologies, products, APIs and infrastructure extensions. According to the author, service-orientation as a paradigm can be
represented by eight main design principles:
- Standardized Service Contract
- Service Loose Coupling
- Service Abstraction
- Service Reusability
- Service Autonomy
- Service Statelessness
- Service Discoverability
- Service Composability
Initially, the book start discussing about characteristics, patterns, concepts, principles and standards in order to explain how these entities are associated to compose a paradigm. Then, service-orientation paradigm as well as services, web-services, SOA are introduced. Finally, some benefits of design applications using service-orientation principles instead of traditional software development principles are presented. This part is described by the first 122 pages, the whole book can be considered a theoretical approach, but since this first part focus on the basis of Software design and architecture, it is very useful as bibliography references.
The rest of the book is more direct and presents the eight design principles supported by the case study of Cutisaws, a manufacturer of chainsaws. This company was growing faster, consequently its IT department had to be improved, otherwise its growing would be affected. Furthermore, Cutisaws was not inclined to invest a massive amount of capital in a new IT's Plataform. The solution was modeling a environment using SOA. In this part of book, each principle is treated by one chapter which presents its definitions, goals, design characteristics and implementation requirements, by the end of chapter it is explained how that principle presented was applied in the Cutisaws solution.
The book is recommended for those who wants to study design principles of service-oriented paradigm and how/where these principles should be applied to design services for SOA. Since, the book is not focused on specific technologies and practical aspects, it is a helpful source for consulting and bibliography reference.
Obs: I didn't read the whole book, just 200 pages.
