2004
DOI: 10.1023/b:clus.0000039493.73008.13
|View full text |Cite
|
Sign up to set email alerts
|

Towards Real-Time Fault-Tolerant CORBA Middleware

Abstract: An increasing number of applications are being developed using distributed object computing (DOC)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
19
0

Year Published

2008
2008
2012
2012

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 32 publications
(19 citation statements)
references
References 44 publications
0
19
0
Order By: Relevance
“…Receiving the right answer too late becomes the wrong answer (Gokhale 2004). Run time error and exception handling in the development phase; typically require a different set of tasks to be initiated when an error occurs (Westley 2004).…”
Section: Modelling Agent Real-time Constraintsmentioning
confidence: 99%
“…Receiving the right answer too late becomes the wrong answer (Gokhale 2004). Run time error and exception handling in the development phase; typically require a different set of tasks to be initiated when an error occurs (Westley 2004).…”
Section: Modelling Agent Real-time Constraintsmentioning
confidence: 99%
“…Similar to the COLD PASSIVE replication style used in FaultTolerant CORBA (FT-CORBA) [15], all subtasks are assumed to be stateless (except the connections between subsequent subtasks which are maintained by the middleware) so that the overhead of active state synchronization is avoided. The migration mechanism works as follows: Each subtask can have a primary instance and a few backup instances on the processors where it has the required resource.…”
Section: Middleware Implementationmentioning
confidence: 99%
“…We look at the two important characteristics of distributed stream processing applications, namely the fact that they are composite and strict, to understand their availability requirements that differentiate them from other distributed applications, and to guide our placement decisions. In many distributed applications such as distributed storage [2,4,17,30] or client/server computing [6,12,14,18,20,25,36] that focus on the availability of individual objects, such as files or processes, an increase in the number of replicas usually implies a similar increase in the availability of the application. While we expect that increasing the number of component replicas will also increase the availability of a distributed stream processing application composed of them, we find that this increase greatly depends on the relative placement of the individual component replicas.…”
Section: Maximizing Application Availabilitymentioning
confidence: 99%
“…Replication for high availability and fault tolerance has been studied from different perspectives in a variety of domains, including distributed databases [13,22,24,34], distributed object systems [11,12,14,18,21,25,36], and web services [6,20]. While many aspects of replication have been studied extensively, and solutions such as active [31] and passive [9] replication are widely accepted, in this work we focus on replica placement for maximizing the availability of distributed stream processing applications.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation