![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello all, I have two fundamental questions regarding the requirements for a Berkeley DB replication transport protocol: - is out-of-order reception of messages permitted? - is loss of messages permitted? |
|
To be concrete: would it be sufficient to use plain UDP, maybe augmented with a good message authenticator, without regard to retransmission and sequencing? |
#3
| |||
| |||
|
|
I have two fundamental questions regarding the requirements for a Berkeley DB replication transport protocol: - is out-of-order reception of messages permitted? - is loss of messages permitted? Yes, and yes. To be concrete: would it be sufficient to use plain UDP, maybe augmented with a good message authenticator, without regard to retransmission and sequencing? Berkeley DB replication was carefully designed to be transport mechanism agnostic, that is, we wanted to be able to run using TCP/IP, UDP, backplane message passing protocol, or carrier pigeon. |
|
Obviously, this has serious implications for the application's transactional guarantees: if the message didn't arrive at the replica, should the master return to the application that the transaction has committed? This means applications requiring serious transactional guarantees will have to do more work when using transport protocols that are lossy, for example. |
#4
| |||
| |||
|
|
I have two fundamental questions regarding the requirements for a Berkeley DB replication transport protocol: |
![]() |
| Thread Tools | |
| Display Modes | |
| |