Event-based Customization of Multi-tenant SaaS Using Microservices

Popular enterprise software such as ERP, CRM is now being made available on the Cloud in the multi-tenant Software as a Service (SaaS) model. The added values come from the ability of vendors to enable customer-specific business advantage for every different tenant who uses the same main enterprise software product. Software vendors need novel customization solutions for Cloud-based multi-tenant SaaS. In this paper, we present an event-based approach in a non-intrusive customization framework that can enable customization for multi-tenant SaaS and address the problem of too many API calls to the main software product. The experimental results on Microsoft’s eShopOnContainers show that our approach can empower an event bus with the ability to customize the flow of processing events, and integrate with tenant-specific microservices for customization. We have shown how our approach makes sure of tenant-isolation, which is crucial in practice for SaaS vendors. This direction can also reduce the number of API calls to the main software product, even when every tenant has different customization services.publishedVersio

Variability in Multi-Tenant Enterprise Software

Enterprise software applications have changed significantly over the last decades. Increasingly, software is deployed in a central location to be accessed through the internet, instead of installing software at end-users. Having software in a central location enables multi-tenancy, where multiple customers transparently share a system’s resources. Currently, multi-tenancy is a popular way to offer functionality of a software product through the internet to numerous customers, offering many advantages to both software vendors and customers. A challenge in this domain is offering variable features to multiple customers. This dissertation provides software architecture patterns for the realization of variability in multi-tenancy settings, in the domain of online enterprise software. The results support software architects on structuring the decision making process by providing a collection of multi-tenant architecture and variability patterns, guidelines for pattern selection, and a model to setup pattern evaluation and comparison sessions. The results reported have been gathered from case studies at software companies and evaluated by experts from the software industry. With these artifacts in hand, software architects can make well-informed decisions and find appropriate patterns for their specific situation, solving the challenges involved in selecting an architecture that supports multi-tenant online enterprise software. Also, these research results contribute to academia by reporting on numerous case studies in an emerging domain and presenting a vocabulary for further and more extensive research

The role of variability patterns in multitenant business software

Abstract-Within the business software domain it is crucial for a software vendor to comply to different customer requirements. Traditionally this could be done by offering different products to different customers, but because multitenant business software deployments use one software product to serve all customers, this is no longer possible. Software vendors have to make sure that one instance of a software product is variable enough to support all different requirements from all different customers. This ability is defined as tenantbased variability. Within this paper a conceptual model is presented, explaining the role software patterns play in solving variability implementation problems in multi-tenant business software. Different important aspects of patterns are explained, like forces and consequences and are linked to concepts in the problem domain. The paper suggests that variability patterns play a large role in addressing variability in multitenant business software and provide a valuable vocabulary for researching, reporting, thinking and communicating about variability solutions in online software products

Variability in Multi-Tenant Enterprise Software

Enterprise software applications have changed significantly over the last decades. Increasingly, software is deployed in a central location to be accessed through the internet, instead of installing software at end-users. Having software in a central location enables multi-tenancy, where multiple customers transparently share a system’s resources. Currently, multi-tenancy is a popular way to offer functionality of a software product through the internet to numerous customers, offering many advantages to both software vendors and customers. A challenge in this domain is offering variable features to multiple customers. This dissertation provides software architecture patterns for the realization of variability in multi-tenancy settings, in the domain of online enterprise software. The results support software architects on structuring the decision making process by providing a collection of multi-tenant architecture and variability patterns, guidelines for pattern selection, and a model to setup pattern evaluation and comparison sessions. The results reported have been gathered from case studies at software companies and evaluated by experts from the software industry. With these artifacts in hand, software architects can make well-informed decisions and find appropriate patterns for their specific situation, solving the challenges involved in selecting an architecture that supports multi-tenant online enterprise software. Also, these research results contribute to academia by reporting on numerous case studies in an emerging domain and presenting a vocabulary for further and more extensive research

Alternatief bestuur openbaar onderwijs en de positie van het directiestatuut.

Item does not contain fulltex

A survey of associate models used within large software ecosystems

Associate models are powerful tools for large software ecosystem orchestrators to manage clusters within its ecosystem. At present, however, it remains unclear how these associate models are used in practice and of what elements such models consist. Without an overview of what associate models consist of, the concept of software ecosystem orchestration will remain elusive. In this paper, a conceptual overview is presented that describes the structure of an ecosystem associate model. The conceptual overview consists of the roles fulfilled by the participant within the associate commitment, including the dimension of the role as well as resulting benefits, requirements and costs. Furthermore, the conceptual overview enables a categorization into different forms of associate model governance, entry barriers and goals for the three respective models. With the conceptual overview, software ecosystem orchestrators can develop their own associate models and attain insight into the forces that are at play in their own software ecosystem