Consistency in a partitioned network: a survey
ACM Computing Surveys (CSUR)
Concurrency control and recovery in database systems
Concurrency control and recovery in database systems
Read-only transactions in a distributed database
ACM Transactions on Database Systems (TODS)
Multiversion concurrency control—theory and algorithms
ACM Transactions on Database Systems (TODS)
Weighted voting for replicated data
SOSP '79 Proceedings of the seventh ACM symposium on Operating systems principles
A principle for resilient sharing of distributed resources
ICSE '76 Proceedings of the 2nd international conference on Software engineering
An optimistic protocol for partitioned distributed database systems
An optimistic protocol for partitioned distributed database systems
Scheduling real-time transactions: a performance evaluation
ACM Transactions on Database Systems (TODS)
Current research on real-time databases
ACM SIGMOD Record
Processing time-constrained aggregate queries in CASE-DB
ACM Transactions on Database Systems (TODS)
Adaptive commitment for distributed real-time transactions
CIKM '94 Proceedings of the third international conference on Information and knowledge management
A time-sensitive object model for real-time systems
ACM Transactions on Software Engineering and Methodology (TOSEM)
An annotated bibliography on real-time database systems
ACM SIGMOD Record
Similarity-Based Load Adjustment for Static Real-Time Transaction Systems
IEEE Transactions on Computers
Real-Time Data Semantics and Similarity-Based Concurrency Control
IEEE Transactions on Computers
| Hi-index | 0.01 |
One of the issues in distributed databases is to maintain the data consistency when a database is replicated for higher availability. In a real-time database system, availability may be more important than consistency since a result must be produced before a deadline. We propose techniques to increase the availability in a partitioned real-time database. We also suggest that a transaction may execute even when the most up-to-date information is not available or when a serializable execution cannot be guaranteed. As long as data integrity is maintained, serializable execution may not be necessary.