> Well as I read back the thread I see 2 different approaches to
> replication:
>
> 1: tight integrated replication.
> pro:
> - bi-directional (or multidirectional): updates are possible everywhere
> - A cluster of servers allways has the same state.
> - it does not matter to which server you connect
> con:
> - network between servers will be a bottleneck, especially if it is a
> WAN connection
> - only full replication possible
I do not understand that point, if it is trigger based, you
have all the flexibility you need. (only some tables, only some rows,
different rows to different targets ....),
(or do you mean not all targets, that could also be achieved with triggers)
> - what happens if one server is down? (or the network between) are
> commits still possible
No, updates are not possible if one target is not reachable,
that would not be synchronous and would again need business rules
to resolve conflicts.
Allowing updates when a target is not reachable would require admin
intervention.
Andreas
