Implementing fault-tolerant services using the state machine approach: a tutorial
ACM Computing Surveys (CSUR)
Principled design of the modern Web architecture
ACM Transactions on Internet Technology (TOIT)
Understanding Replication in Databases and Distributed Systems
ICDCS '00 Proceedings of the The 20th International Conference on Distributed Computing Systems ( ICDCS 2000)
Architectural styles and the design of network-based software architectures
Architectural styles and the design of network-based software architectures
Extending the Representational State Transfer (REST) Architectural Style for Decentralized Systems
Proceedings of the 26th International Conference on Software Engineering
Towards JMS Compliant Group Communication - A Semantic Mapping
NCA '04 Proceedings of the Network Computing and Applications, Third IEEE International Symposium
WS-replication: a framework for highly available web services
Proceedings of the 15th international conference on World Wide Web
What service replication middleware can learn from object replication middleware
Proceedings of the 1st workshop on Middleware for Service Oriented Computing (MW4SOC 2006)
A step towards a new generation of group communication systems
Proceedings of the ACM/IFIP/USENIX 2003 International Conference on Middleware
| Hi-index | 0.00 |
Service resilience, defined as the continued availability of a service despite failures and other negative changes in its environment, is vital in many systems. It is typically achieved by state machine replication using group communication middleware for coordination of service replicas. In this paper we focus on systems that represent critical data as Web resources identified by Uniform Resource Identifiers (URIs). The best examples of such systems are RESTful web services. We present RESTGroups : a group communication front-end for RESTful web services. Our system is based on Spread --- a popular group communication toolkit. Contrary to Spread and other such toolkits, we represent group communication services as resources on the Web, addressed by URIs. In the paper, we describe the system architecture and the API.