Proceedings of the 23rd International Conference on World Wide Web 2014
DOI: 10.1145/2567948.2579218
|View full text |Cite
|
Sign up to set email alerts
|

Seven challenges for RESTful transaction models

Abstract: The REpresentational State Transfer (REST) architectural style describes the design principles that made the World Wide Web scalable and the same principles can be applied in enterprise context to do loosely coupled and scalable application integration. In recent years, RESTful services are gaining traction in the industry and are commonly used as a simpler alternative to SOAP Web Services.However, one of the main drawbacks of RESTful services is the lack of standard mechanisms to support advanced quality-ofse… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
4
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 7 publications
(13 citation statements)
references
References 19 publications
0
13
0
Order By: Relevance
“…58,59 However, because of the REST constraints (uniform interface, resource identification, stateless interaction, self-descriptive messages, and hypermedia as the engine of application state), 60 it is hard to reach ACID constrains for RESTful services without violating those REST constrains. 58,59 However, because of the REST constraints (uniform interface, resource identification, stateless interaction, self-descriptive messages, and hypermedia as the engine of application state), 60 it is hard to reach ACID constrains for RESTful services without violating those REST constrains.…”
Section: Acid Properties Relaxing Models: Review and Comparisonmentioning
confidence: 99%
“…58,59 However, because of the REST constraints (uniform interface, resource identification, stateless interaction, self-descriptive messages, and hypermedia as the engine of application state), 60 it is hard to reach ACID constrains for RESTful services without violating those REST constrains. 58,59 However, because of the REST constraints (uniform interface, resource identification, stateless interaction, self-descriptive messages, and hypermedia as the engine of application state), 60 it is hard to reach ACID constrains for RESTful services without violating those REST constrains.…”
Section: Acid Properties Relaxing Models: Review and Comparisonmentioning
confidence: 99%
“…Transaction processing is one of the essential features of such an enterprise application, since they perform computationally intensive work [15] [19]. For the transaction processing to happen efficiently and effectively, considerable amounts of resources are required to complete execution in a reasonable timeframe [14].…”
Section: Transaction Processing In Resource-intensive Applicationsmentioning
confidence: 99%
“…For the transaction processing to happen efficiently and effectively, considerable amounts of resources are required to complete execution in a reasonable timeframe [14]. Each time a transaction is initiated it creates the demand for a resource [19] and there are instances where two or more workloads can place a demand for the resources at the same time. We deduce that for the extended time such a workload is running it will be assigned available resources and will consume the resources until its execution is complete which could lead to other applications being denied or put on hold (waiting) since the resource is committed elsewhere.…”
Section: Transaction Processing In Resource-intensive Applicationsmentioning
confidence: 99%
“…Single sign-on and delegation of authorities also lie exterior of their space. The paper [5] provides a brief theory on the challenges that are identified on using of REST APIs. The paper provides concepts and methodologies of Aspect oriented programming.…”
Section: Literature Surveymentioning
confidence: 99%