Michael:
1: It will probably need a messaging system that can properly
register/unregister a backend database system. a SIP like syntax comes
into mind. (or a XML message, for the ease of future expansion)
2: What do you mean by "per-database basis"? Database as the concept of
database schema? or seperate physical database server?
3: How does the proxy server know that a backend server failed in commit?
Wei
Michael A Nachbaur wrote:
>LOL! Depending on how much FUD I can throw at the guys higher up in the food
>chain at my office, I might be able to get some budget space to develop
>something like this. There are some significant technical hurdles I have to
>overcome, but I think it's doable. The analogy I came up with is SCSI RAID
>for databases. You can rip a database server out, and the overall system
>will still function...toss it back in, and updates will still happen. I
>would also like to be able to throw a fresh database in place and have it
>mirror the existing database servers in the background so you don't have to
>go through the complicated procedure of dumping/restoring the database
>servers by hand.
>
>Re: FIFO, yeah, I realized that after I sent the message.
>
>Does anyone have any ideas for me on this? I think it might make sense to use
>PostgreSQL as the storage mechanism for the proxy server, but that sort of
>defeats the purpose of having a replication system. Maybe spread can be used
>to distribute the messages to different servers, but I'm not too familiar
>with it.
>
>Also, one final note, I'm a Perl programmer, so anything I build will be
>written in that. If anyone has objections, let me know and maybe we could
>work together on something.
>
>
>
