Myles Wakeham schrieb am 09.03.2011 um 10:11 (-0700):

> I'd like to adopt a common approach that MySQL databases & high
> demand PHP apps seem to do, and that is that updates to the
> database are immediately replicated to all node systems, which
> have their own separate Firebird database on them.

Replication is not built into Firebird, but available separately.

> In this way, each node is self-contained. If a node is down,
> however, I need to find a way to identify changes that were made
> to a 'master' server, that didn't complete replication to a
> number of slave node servers.
>
> Is anyone doing this sort of thing in similar technologies that
> we use? If so, how have you chosen to do it? Should I build all
> of this technology myself, or are there any pre-written systems
> that do replication that already are considered 'bullet proof'
> that I should be considering evaluation?

I'd consider one of the existing solutions:

How to do replication of Firebird databases?
http://www.firebirdfaq.org/faq249/

I'm not familiar with any of those, but for mission-critical
software I'd probably go for a commercial solution.

--
Michael Ludwig