Soa methodology
- 2. Overview • One of the greatest challenges to carrying out successful SOA projects is in understanding how they should be carried out. Without being able to rely on proven processes and practices, an SOA initiative can turn into a high-risk venture because you simply may not know what to expect. • A sound methodology can alleviate this risk by providing a solid foundation from where you can shape a delivery approach that accommodates your goals and requirements while also laying out a path to realizing the benefits of SOA and service-oriented computing.
- 3. Service Layers • When building various types of services, it becomes evident that they can be categorized depending on: • the type of logic they encapsulate • the extent of reuse potential this logic has • how this logic relates to existing domains within the enterprise
- 4. • As a result, there are three common service classifications that represent the primary service models used in SOA projects: • Entity Services • Task Services • Utility Services
- 5. Entity Services • In just about every enterprise, there will be business model documents that define the organization's relevant business entities. Examples of business entities include customer, employee, invoice, and claim.
- 6. Task Services • A business service with a functional boundary directly associated with a specific parent business task or process is based on the task service model. This type of service tends to have less reuse potential and is generally positioned as the controller of a composition responsible for composing other, more process-agnostic services.
- 7. Utility Services • Each of the previously described service models has a very clear focus on representing business logic. However, within the realm of automation, there is not always a need to associate logic with a business model or process. In fact, it can be highly beneficial to deliberately establish a functional context that is non-business-centric.