Advertisement

Service Aggregation Using Relational Operations on Interface Parameters

  • George Feuerlicht
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4652)

Abstract

Many practitioners recommend the use of coarse-grained services that minimize the number of messages and avoid the need to maintain state information between invocations. However, when considered from a software engineering perspective, coarse-grained services suffer from a number of significant drawbacks, including limited reuse and difficult composability. An important challenge for the developers of service-oriented applications is to determine appropriate level of service granularity to ensure that services are reusable and at the same time have good performance characteristics. Decisions about service granularity need to be taken in the context of a methodological framework rather than using ad hoc heuristics. In this paper we describe a method for service aggregation that uses relational operations over interface parameters to assemble services from low granularity atomic service operations. We illustrate the impact of service aggregation on cohesion and coupling using examples and discuss service granularity in the context of application requirements.

Keywords

service design service aggregation relational operations 

References

  1. 1.
    Webber, J., Parastatidis, S.: Realising Service Oriented Architectures Using Web Services (to be published in 2006 in Service Oriented Computing). MIT Press, Cambridge (2006)Google Scholar
  2. 2.
    Feuerlicht, G.: Design of Service Interfaces for e-Business Applications using Data Normalization Techniques. In: Journal of Information Systems and e-Business Management, pp. 1–14. Springer, Heidelberg, ISS:1617-98 (2005)Google Scholar
  3. 3.
    Feuerlicht, G.: Application of Data Engineering Techniques to Design of Messages Structures for Web Services. In: WDSOA 2005. Proceedings of the First International Workshop on Design of Service-Oriented Applications, Amsterdam, The Netherlands, December 12, 2005, IBM Research Report RC23819 (W0512-29) (2005)Google Scholar
  4. 4.
    Stevens, W.P., Myers, G.J., Constantine, L.L.: Structured Design. IBM Systems Journal 38(S2&3) (1999)Google Scholar
  5. 5.
    Myers, G.J.: Composite Structured Design, Van Nostrand Reinhold, 175 (1978), ISBN 0-442-80584-5Google Scholar
  6. 6.
    Codd, E.F.: Normalized Data Structure: A Brief Tutorial. In: Proceedings of 1971 ACM-SIGFIDET Workshop on Data Description, Access and Control, San Diego, California, November 11-12, 1971, pp. 1–17. ACM Press, New York (1971)Google Scholar
  7. 7.
    Date, C.J., Fagin, R.: Simple Conditions for Guaranteeing Higher Normal Forms in Relational Databases. ACM Transactions on Database Systems (TODS) 17(3), 465–476 (1992)CrossRefGoogle Scholar
  8. 8.
    Srivastava, B., Koehler, J.: Web Service Composition - Current Solutions and Open Problems. In: ICAPS (2003)Google Scholar
  9. 9.
    Milanovic, N., Malek, M.: Current Solutions for Web Service Composition. IEEE Internet Computing 8(6), 51–59 (2004), http://dx.doi.org/10.1109/MIC.2004.58 CrossRefGoogle Scholar
  10. 10.
    Peltz, C.: Web Services Orchestration and Choreography. Computer 36(10), 46–52 (2003)CrossRefGoogle Scholar
  11. 11.
    Pasley, J.: How BPEL and SOA Are Changing Web Services Development. IEEE Internet Computing 9(3), 60–67 (2005)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2007

Authors and Affiliations

  • George Feuerlicht
    • 1
  1. 1.Faculty of Information Technology, University of Technology, Sydney, P.O. Box 123 Broadway, Sydney, NSW 2007Australia

Personalised recommendations