2012
DOI: 10.4018/jwsr.2012040102
|View full text |Cite
|
Sign up to set email alerts
|

A Scalable Multi-Tenant Architecture for Business Process Executions

Abstract: Cloud computing, as a concept, promises cost savings to end-users by letting them outsource their non-critical business functions to a third-party in pay-as-you-go style. However, to enable economic pay-as-you-go services, the end-users need Cloud middleware that maximizes sharing and support near-zero cost for unused applications. Multi-tenancy, which let multiple tenants to share a single application instance securely, is a key enabler for building such a middleware. On the other hand, Business processes cap… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2015
2015
2021
2021

Publication Types

Select...
6
1
1

Relationship

1
7

Authors

Journals

citations
Cited by 12 publications
(11 citation statements)
references
References 13 publications
0
11
0
Order By: Relevance
“…The messages and their interpretations (ie, events and recorded states) carry the flow information (eg, the identifiers of the relevant entities). This flow information allows the enactment engine to isolate the executions of a given composite application by the end users of different tenants (similar to the use of the tenant‐context in the work of Pathirage et al for tenant execution isolation).…”
Section: The Sdsn@rt Middleware Environmentmentioning
confidence: 99%
See 1 more Smart Citation
“…The messages and their interpretations (ie, events and recorded states) carry the flow information (eg, the identifiers of the relevant entities). This flow information allows the enactment engine to isolate the executions of a given composite application by the end users of different tenants (similar to the use of the tenant‐context in the work of Pathirage et al for tenant execution isolation).…”
Section: The Sdsn@rt Middleware Environmentmentioning
confidence: 99%
“…In the first stage, when the routing REP of the user role receives an instantiation Web service request, the routing REP locates the regulation rules for the VSN via the regulation table. The Web service request contains the identifier of the VSN encoded in a message header or the part of the Web service endpoint reference of the user role (similar to the use of the tenant identifier in the work of Pathirage et al). The VSN identifier is the key to the regulation table.…”
Section: The Sdsn@rt Middleware Environmentmentioning
confidence: 99%
“…It can be obtained from the execution engine of the SOS by calculating the time difference between the arrival of user requests and the delivery of corresponding outcomes. This is feasible because the execution engine that invokes the distributed services is centrally managed by the SOS provider [38]. Each request will traverse one execution scenario, depending on the runtime decisions made in the branch structures of the SOS.…”
Section: Similarity Coefficientmentioning
confidence: 99%
“…In the past decade, many approaches for quality-aware service selection have been proposed to compose single tenant SOSs [1]- [3], [37] and multi-tenant SOSs [6], [20], [25], [28], including ours [32], [18]. However, none of the existing approaches has systematically considered three critical issues that challenge their success rates of finding a solution: 1) multi-tenancy, i.e., the ability for an SOS to serve multiple tenants simultaneously based on a single application instance; 2) provider competition, the competition between service providers has not been fully explored in the open and competitive cloud environment; and 3) service complementarity, i.e., the complementarity between the quality of multiple services.…”
Section: Introductionmentioning
confidence: 99%