A distributed service-oriented architecture for business process execution
ACM Transactions on the Web (TWEB)
Efficacy of techniques for responsiveness in a wide-area publish/subscribe system
Proceedings of the 11th International Middleware Conference Industrial track
GPX-matcher: a generic boolean predicate-based XPath expression matcher
Proceedings of the 14th International Conference on Extending Database Technology
End-to-end reliability for best-effort content-based publish/subscribe networks
Proceedings of the 5th ACM international conference on Distributed event-based system
Middleware support for internetware: a service perspective
Proceedings of the Second Asia-Pacific Symposium on Internetware
Trustworthy and resilient monitoring system for cloud infrastructures
Proceedings of the Workshop on Posters and Demos Track
Introducing Publiy: a multi-purpose distributed publish/subscribe system
Proceedings of the Posters and Demo Track
Building a reliable and high-performance content-based publish/subscribe system
Journal of Parallel and Distributed Computing
Opportunistic multipath forwarding in content-based publish/subscribe overlays
Proceedings of the 13th International Middleware Conference
Survey On reliability in publish/subscribe services
Computer Networks: The International Journal of Computer and Telecommunications Networking
DYNATOPS: a dynamic topic-based publish/subscribe architecture
Proceedings of the 7th ACM international conference on Distributed event-based systems
Towards Byzantine fault tolerant publish/subscribe: a state machine approach
Proceedings of the 9th Workshop on Hot Topics in Dependable Systems
| Hi-index | 0.00 |
This paper develops reliable distributed publish/subscriber algorithms with service availability in the face of concurrent crash failure of up to $\delta$ brokers. The reliability of service in our context refers to per-source in-order and exactly-once delivery of publications to matching subscribers. To handle failures, brokers maintain data structures that enable them to reconnect the topology and compute new forwarding paths on the fly. This enables fast reaction to failures and improves the system's availability. Moreover, we present a recovery procedure that recovering brokers execute in order to re-enter the system, and synchronize their routing information.