| From: | Scott Ribe <scott_ribe(at)killerbytes(dot)com> |
|---|---|
| To: | Steve Manes <smanes(at)magpie(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Asychronous database replication |
| Date: | 2005-09-16 16:58:56 |
| Message-ID: | BF5055F0.3181E%scott_ribe@killerbytes.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> The requirements scream ASP model except that this system needs to be
> functional for disaster management where it's likely there won't be any
> communications. At least, that's the constraint I've been given.
I'm not an expert on this, but just kicking around the idea, the approach I
think I'd look into:
- clients don't access the database directly
- there's a middleware layer and clients make higher-level RPC-type calls
whose semantics more closely match the client functionality
- then those calls can be logged and replicated...
--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 665-7007 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2005-09-16 17:09:57 | Re: Replication |
| Previous Message | Thomas O'Connell | 2005-09-16 15:02:28 | Re: Question about a query plan |