Software Architecture Driven Configurability of Multi-tenant SaaS Application 419 Internet. Compared to traditional software delivery, SaaS service can always be ac-cessed where there is Internet. According to actual requirements, tenants lease software service. The SaaS delivery model essentially separates software ownership from the user—the owner is a vendor who hosts the software and lets the tenant execute it on-demand through some form of client-side architecture via the Internet or an Intranet[2].
SaaS serves for multiple tenants with a list of business services to be delivered. The key of SaaS software architecture with multi-tenant is to isolate data among of differ-ent tenants. The strategy guarantees that different tenants share the same running in-stance of SaaS application and that independent personal experience of application and data space are provided. The configurability of SaaS application can be implemented by software architecture driven model by using relevant architectural element---connector. In the context of multi-tenant, software architecture driven configurability mainly includes function configurability and user interface configurability.
The characteristics of the SaaS configurability have resulted in a recent drive to revisit the design of software architecture and challenges resulting from SaaS application. Software architecture provides a whole guideline to create target system, including specification of architectural elements, constraint of components and com-munication contract between architectural elements and software surviving environ-ment. Existing approaches have made configurability strategies with external model that used formal methods, such as[3, 4]. The proposed method is novel because of it utilizes the software architecture as a lever to coordinate between functional architec-tural elements and configurability components. By employing AOP (Aspect-oriented Programming)[5], the method regards configurability as a crosscutting to realize con-figurability of SaaS application.
The remainder of this paper is organized as follows: Section II introduces the con-figurability of SaaS application. We discuss the function configurability and user inter-face configurability in our context. In Section III, configurability connector based on AOP is designed. In Section IV, we report on a case study on configurability method based on software architecture and Section V discusses conclusions and directions for future works.
2 Configurability of SaaS Application
There are a variety of different aspects about the configuration function between tra-ditional product-based configuration and tenant-based configuration as illustrated in Table 1.
Table 1. Compare between traditional troduct-based and tenant-based configuration
Item
Relevant
Configuration Occasion
Configuration Quantity
Role of configuration
Scope Load time Product-based configuration Relevant to product features Before running system One for the whole system Service engineer Valid for the whole system Initial phase of system Tenant-based configuration Relevant to tenant features At runtime of system One for each tenant Tenant administrator Only valid for tenant data Dynamic loading at runtime
-sharing multi-tenant data storage architecture. ...premise software are presented in depth in [1, ... configurability, scalability, and extensibility ...
Architecture of SaaS business process customization ...configurability management, concrete service selection...Kuo, “A Policy-Driven Approach for Software-as...
Architecture of SaaS business process customization ...configurability management, concrete service selection...Kuo, “A Policy-Driven Approach for Software-as...
热门文档