Integrating Service Matchers into a Service Market Architecture

  • Marie Christin Platenius
  • Steffen Becker
  • Wilhelm Schäfer
Part of the Lecture Notes in Computer Science book series (LNCS, volume 8627)


Service markets provide software components in the form of services. In order to enable a service discovery that satisfies service requesters and providers best, markets need automatic service matching: approaches for comparing whether a provided service satisfies a service request. Current markets, e.g., app markets, are limited to basic keyword-based search although many better suitable matching approaches are described in literature. However, necessary architectural decisions for the integration of matchers have a huge impact on quality properties like performance or security.

Architectural decisions wrt. service matchers have rarely been discussed, yet, and systematic approaches for their integration into service markets are missing. In this paper, we present a systematic integration approach including the definition of requirements and a discussion on architectural tactics. As a benefit, the decision-making process of integrating service matchers is supported and the overall market success can be improved.


Service Matching Service Markets Software Architecture On-The-Fly Computing 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Amazon Web Services. Website, (last access: June 2014)
  2. 2.
    Bachmann, F., Bass, L., Klein, M.: Deriving architectural tactics: A step toward methodical architectural design. Technical report, Software Engineering Institute, Carnegie Mellon University, CMU/SEI-2003-TR-004 (2003)Google Scholar
  3. 3.
    Chinnici, R., Moreau, J.-J., Ryman, A., Weerawarana, S.: Web Services Description Language Version 2.0 Part 1: Core Language. Technical report (2007)Google Scholar
  4. 4.
    Dong, H., Hussain, F.K., Chang, E.: Semantic Web Service matchmakers: state of the art and challenges. In: Concurrency and Computation: Practice and Experience, vol. 25, pp. 961–988. Wiley Online Library (2012)Google Scholar
  5. 5.
    Google. Google Play - Website, (last access: June 2014)
  6. 6.
    Herbst, N.R., Kounev, S., Reussner, R.: Elasticity: What it is, and What it is Not. In: 10th Int. Conf. on Autonomic Computing. USENIX (2013)Google Scholar
  7. 7.
    Klusch, M.: Semantic web service coordination. In: CASCOM: Intelligent Service Coordination in the Semantic Web, pp. 59–104. Springer (2008)Google Scholar
  8. 8.
    O’Sullivan, J., Edmond, D., ter Hofstede, A.H.M.: Service description: A survey of the general nature of services. Distributed and Parallel Databases Journal (2002)Google Scholar
  9. 9.
    Platenius, M.C., Becker, S., Schäfer, W.: Integrating Service Matchers into a Service Market Architecture. Technical Report tr-ri-14-340, Heinz Nixdorf Institute (2014)Google Scholar
  10. 10.
    Platenius, M.C., von Detten, M., Becker, S., Schäfer, W., Engels, G.: A Survey of Fuzzy Service Matching Approaches in the Context of On-The-Fly Computing. In: 16th Int. Symposium on Component-based Software Engineering. ACM (2013)Google Scholar
  11. 11., Inc., Salesforce AppExchange, (last access: June 2014)
  12. 12.
    Schlauderer, S., Overhage, S.: How Perfect are Markets for Software Services? An Economic Perspective on Market Deficiencies and Desirable Market Features. In: Proc. of the 19th European Conf. on Information Systems (2011)Google Scholar
  13. 13.
    StrikeIron. StrikeIron - Website, (last access: June 2014)
  14. 14.
    The Eclipse Foundation. Eclipse Marketplace, (last access: June 2014)
  15. 15.
    W3C. Web services architecture, (last access: June 2014)

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Marie Christin Platenius
    • 1
  • Steffen Becker
    • 1
  • Wilhelm Schäfer
    • 1
  1. 1.Software Engineering Group, Heinz Nixdorf InstituteUniversity of PaderbornGermany

Personalised recommendations