On the Definition of Service Granularity and Its Architectural Impact

  • Authors:

  • Raf Haesen;Monique Snoeck;Wilfried Lemahieu;Stephan Poelmans

  • Affiliations:

  • Department of Decision Sciences & Information Management, Katholieke Universiteit Leuven, Belgium and Hogeschool-Universiteit Brussel, Belgium;Department of Decision Sciences & Information Management, Katholieke Universiteit Leuven, Belgium;Department of Decision Sciences & Information Management, Katholieke Universiteit Leuven, Belgium;Hogeschool-Universiteit Brussel, Belgium

  • Venue:
  • CAiSE '08 Proceedings of the 20th international conference on Advanced Information Systems Engineering
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

Abstract

Service granularity generally refers to the size of a service. The fact that services should be large-sized or coarse-grained is often postulated as a fundamental design principle of service oriented architecture (SOA). However, multiple meanings are put on the term granularity and the impact of granularity on architectural qualities is not always clear. In order to structure the discussion, we propose a classification of service granularity types that reflects three different interpretations. Firstly, functionality granularityrefers to how much functionality is offered by a service. Secondly, data granularityreflects the amount of data that is exchanged with a service. Finally, the business value granularityof a service indicates to which extent the service provides added business value. For each of these types, we discuss the impact of granularity on a set of architectural concerns, such as performance, reusability and flexibility. We illustrate each granularity type with small examples and we present some preliminary ideas of how controlling granularity may assist in alleviating some architectural issues as we encounter them in a large-sized bank-insurance company that is currently migrating to SOA.