Comparing Service-Oriented and Distributed Object Architectures

Baker, Sean; Dobson, Simon

doi:10.1007/11575771_40

Cited by 25 publications

(13 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As different middleware has different advantages, many enterprises used various middleware for their application integration over the years. As a result, these enterprises face "Middleware Islands" issue caused by multiple middleware approaches because middleware technologies and products from different vendors don't interoperate easily [35]. As a result, enterprises have to find ways to integrate these different middleware systems.…”

Section: Web Services Service-oriented Architecture and Enterprismentioning

confidence: 99%

“…But in many cases, this isn't possible due to reasons such as lack of technical expertise and costs [2]. Web Services and its underlying principle named Service-oriented architecture are considered good solutions for such middleware-to-middleware interworking [2], [35].…”

Section: Web Services Service-oriented Architecture and Enterprismentioning

confidence: 99%

“…In SOA, software applications are packaged as services. Each service has a well-defined interface which lists the operations it provides and the set of messages it accepts and sends in response [35]. Services can be reconstructed and reused to create new applications [8].…”

Section: Web Services Service-oriented Architecture and Enterprismentioning

confidence: 99%

See 2 more Smart Citations

Integration of Distributed Enterprise Applications: A Survey

2014

IEEE Trans. Ind. Inf.

255

View full text Add to dashboard Cite

Section: Web Services Service-oriented Architecture and Enterprismentioning

confidence: 99%

Section: Web Services Service-oriented Architecture and Enterprismentioning

confidence: 99%

See 1 more Smart Citation

Integration of Distributed Enterprise Applications: A Survey

2014

IEEE Trans. Ind. Inf.

255

View full text Add to dashboard Cite

“…Given the differences between services and distributed objects in terms of granularity, interface types, composition and identification [3], we argued that it was necessary to extend established software measurement and related models before applying them to the domain of SOS. Note that it has been argued before, in the domain of web applications, that traditional models and metrics should be re-assessed before being applied to a new domain [20].…”

Section: Background and Related Workmentioning

confidence: 99%

Software adaptation for service-oriented systems

Rossi

Tari

2006

Proceedings of the 1st Workshop on Middleware for Service Oriented Computing (MW4SOC 2006)

View full text Add to dashboard Cite

Mobile services operate on hosts with diverse capabilities, in heterogeneous networks, where the usage of resources, such as processor, memory and network, is constantly changing. In order to maintain efficiency, in terms of performance and resource utilization, such services should be able to adapt to changes in their environment.This paper proposes and empirically evaluates an application transparent adaptation strategy for service-oriented systems. The strategy is based upon the solution of an optimization model derived from an existing suite of metrics for services, which maps system services to network nodes.The strategy is evaluated empirically using a number of distinct scenarios involving runtime changes in processor, memory and network utilization. In order to maintain execution efficiency in response to these changing operating conditions, the strategy rearranges the service topology of the system dynamically by moving services between network nodes. The results show that the negative impact of environmental changes on runtime efficiency can be reduced, after adaptation, from 33% to 100% depending on the selected parameters.

show abstract

“…Com isso, as chances de ocorrência de seqüências inválidas de chamadas são maiores e, portanto, a incorporação explícita de código nos clientes para detectar tais chamadas evita que elas sejam transmitidas pela Web e processadas em servidores remotos. Existe ainda uma tendência que interfaces de serviços Web tenham "maior granularidade" -istoé, tenham mais métodos complexos -que interfaces de aplicações tradicionais baseadas em objetos distribuídos [4]. Esta tendência também motivou a incorporação de protocolos de invocação em SmartWS.…”

Section: Protocolo De Invocaçãounclassified

Invocation of replicated web services using smart proxies

Carmo

Valente

2006

Proceedings of the 12th Brazilian Symposium on Multimedia and the Web

View full text Add to dashboard Cite

Smart proxies are objects often used to adapt and customize distributed object-oriented systems in a non-invasive way. For example, smart proxies are common used to provide support to quality of service attributes. In this paper, we investigate the use of smart proxies in order to provide replication transparency in middleware systems that support the implementation of Web services. The system presented in the paper, called SmartWS, supports the prime replicated server selection policies proposed in the literature. The paper also provides guidelines that help Web service users to choose the policy more suitable to a given application. A new server selection policy that combines several advantages of the already proposed policies is also described. The paper also presents results obtained from experiments performed with a prototype implementation of SmartWS. Such results reinforce the policy selection guidelines presented in the paper.

show abstract

Comparing Service-Oriented and Distributed Object Architectures

Cited by 25 publications

References 6 publications

Integration of Distributed Enterprise Applications: A Survey

Integration of Distributed Enterprise Applications: A Survey

Software adaptation for service-oriented systems

Invocation of replicated web services using smart proxies

Contact Info

Product

Resources

About