Technologies for Web and cloud service interaction: a survey

Lampesberger, Harald

doi:10.1007/s11761-015-0174-1

Cited by 37 publications

(39 citation statements)

References 136 publications

(160 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A broker reduces the communication complexity between a numbers of peers but can incur delays in real-time applications because an additional storeand-forward procedure is necessary. [3] a) b)…”

Section: Message-oriented Middlewarementioning

confidence: 99%

“…Due to the transport-agnostic design of SOAP/WS-* services, a MOM can also serve as a transport mechanism for SOAP messages. [3] Java Message Service…”

Section: Message-oriented Middlewarementioning

confidence: 99%

“…[3] Advanced Message Queuing Protocol Historically, MOM solutions have relied on proprietary protocols, and JMS is an attempt to agree on a compatible interface. Interoperability between varying MOM solutions is still difficult; costly JMS adapters or bridges are necessary to connect different transport mechanisms.…”

Section: Message-oriented Middlewarementioning

confidence: 99%

“…Depending on the exchange type and bindings, the message is delivered to queues, where consumers can fetch it from (a) direct exchange; (b) topic exchange; (c) fan-out exchange; (d) headers exchange. [3] …”

Section: Message-oriented Middlewarementioning

confidence: 99%

“…Rackspace Cloud Queues [80] supports publish-subscribe architectures by a HTTP based RESTful API in the spirit of RestMS. [3] ZeroMQ and Nanomsg…”

Section: Polyglot Message Brokersmentioning

confidence: 99%

See 4 more Smart Citations

State-Of-The-Art of Messaging for Distributed Computing Systems

Celar¹,

Mudnić²,

Seremet³

2016

Proceedings of the 27th International DAAAM Symposium 2016

View full text Add to dashboard Cite

Abstract:Modern software applications rarely live in isolation and nowadays it is common practice to rely on services or consume information provided by remote entities. In such a distributed architecture, integration is key. Messaging, for more than a decade, is the reference solution to tackle challenges of a distributed nature, such as network unreliability, strong-coupling of producers and consumers and the heterogeneity of applications. Thanks to a strong community and a common effort towards standards and consolidation, message brokers are today the transport layer building blocks in many projects and services, both within the physics community and outside.Moreover, in recent years, a new generation of messaging services has appeared, with a focus on low-latency and high-performance use cases, pushing the boundaries of messaging applications. This paper will present messaging solutions for distributed applications going through an overview of the main concepts, technologies and services.

show abstract

Section: Message-oriented Middlewarementioning

confidence: 99%

“…Due to the transport-agnostic design of SOAP/WS-* services, a MOM can also serve as a transport mechanism for SOAP messages. [3] Java Message Service…”

Section: Message-oriented Middlewarementioning

confidence: 99%

Section: Message-oriented Middlewarementioning

confidence: 99%

Section: Message-oriented Middlewarementioning

confidence: 99%

“…Rackspace Cloud Queues [80] supports publish-subscribe architectures by a HTTP based RESTful API in the spirit of RestMS. [3] ZeroMQ and Nanomsg…”

Section: Polyglot Message Brokersmentioning

confidence: 99%

See 3 more Smart Citations

State-Of-The-Art of Messaging for Distributed Computing Systems

Celar¹,

Mudnić²,

Seremet³

2016

Proceedings of the 27th International DAAAM Symposium 2016

View full text Add to dashboard Cite

show abstract

Monitoring of Client-Cloud Interaction

Lampesberger

Rady

2015

Correct Software in Web Applications and Web Services

Self Cite

View full text Add to dashboard Cite

When a client consumes a cloud service, computational liabilities are transferred to the service provider in accordance to the cloud paradigm, and the client loses some control over software components. One way to raise assurance about correctness and dependability of a consumed service and its software components is monitoring. In particular, a monitor is a system that observes the behavior of another system, and observation points that expose the target system's state and state changes are required. Due to the cloud paradigm, popular techniques for monitoring such as code instrumentation are often not available to the client because of limited visibility, lack of control, and black-box software components. Based on a literature review, we identify potential observation points in today's cloud services. Furthermore, we investigate two cloud-specific monitoring applications based on our ongoing research. While service level agreement (SLA) monitoring ensures that agreed-upon conditions between clients and providers are met, language-based anomaly detection monitors the interaction between client and cloud for misuse attempts.

show abstract