Book Image

SOA Made Simple

Book Image

SOA Made Simple

Overview of this book

SOA is an industry term which is often preached like a religion rather than taught like a technology, and over time, grasping the concept has become unnecessarily difficult. Many companies proclaim that they don't know where to begin with SOA, while others have begun their SOA effort but haven't reaped the benefits they were convinced it would bring. "SOA Made Simple"ù unveils the true meaning of Service Oriented Architecture and how to make it successful so that you can confidently explain SOA to anyone! "SOA Made Simple"ù explains exactly what SOA is in simple terminology and by using real-life examples. Once a simple definition is clear in your mind, you'll be guided through what SOA solves, when and why you should use it, and how to set up, design and categorize your SOA landscape. With this book in hand you'll learn to keep your SOA strategy successful as you expand on it. "SOA Made Simple"ù demystifies SOA, simply. It is not difficult to grasp, but for various reasons SOA is often made unnecessarily complex. Service-orientation is already a very natural way of thinking for business stakeholders that want to realize and sell services to potential clients, and this book helps you to realize that concept both in theory and practice. You'll begin with a clear and simple explanation of what SOA is and why we need it. You'll then be presented with plain facts about the key ingredients of a service, and along the way learn about service design, layering and categorizing, some major SOA platform offerings as well as governance and successful implementation. After reading "SOA Made Simple"ù you will have a clear understanding of what SOA is so you can implement and govern SOA in your own organization.
Table of Contents (17 chapters)
SOA Made Simple
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Chapter 3. Service Identification and Design

We have seen that services are a key aspect of any SOA, and by now we know exactly what a service is! The next step is for you to find out what services you actually need based on the requirements of clients. This process is called service identification. Once you have identified what services your clients require, you can start designing these services by designing their operations, and the input and output of these operations.

It's important to start with service identification before going into the actual details of service design. Don't start with the design until you have a business case and a real project with real consumers, otherwise you might end up investing a lot of time and money in the design and implementation of services and operations that are useless. If you are not sure whether particular operations are needed, leave them out and only design and implement the ones you need. Later on you can always expand services and add operations...