|
Home > Archive > Slony1 PostgreSQL Replication > June 2005 > metilinx
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Has anyone investigated metilinx as an alternative
replication solution?
Anything good, bad, indifferent about the company
and product (besides not being open source and not
pg specific) would be helpful.
--elein
elein- JkRegAVoul5BDgjK7y7T
UQ@public.gmane.org
| |
| Jan Wieck 2005-06-22, 7:24 am |
| On 6/21/2005 6:46 PM, elein wrote:
> Has anyone investigated metilinx as an alternative
> replication solution?
> Anything good, bad, indifferent about the company
> and product (besides not being open source and not
> pg specific) would be helpful.
From this whitepaper:
http://www.metilinx.com/images/DB_Whitepaper.pdf
which is the most detailed (clear throat) technical information I was
able to find through Google, I conclude that the whole thing acts as a
db proxy that duplicates database traffic on the SQL statement level.
The client applications connect via OLEDB or ODBC to the "replicators".
All replicators communicate with the "sequencer", which determines the
total order of all "SQL statements". The replicators then execute this
total order against all connected databases, returning the result
directly to the client.
Jan
>
> --elein
> elein- JkRegAVoul5BDgjK7y7T
UQ@public.gmane.org
> ____________________
____________________
_______
> Slony1-general mailing list
> Slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
> http://gborg.postgresql.org/mailman.../slony1-general
--
#===================
====================
====================
===========#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#===================
====================
=========== JanWieck- bwPqjjyvM7QAvxtiuMwx
3w@public.gmane.org #
| |
|
| On Wed, Jun 22, 2005 at 06:43:43AM -0400, Jan Wieck wrote:
> On 6/21/2005 6:46 PM, elein wrote:
>
> From this whitepaper:
>
> http://www.metilinx.com/images/DB_Whitepaper.pdf
>
> which is the most detailed (clear throat) technical information I was
> able to find through Google, I conclude that the whole thing acts as a
> db proxy that duplicates database traffic on the SQL statement level.
> The client applications connect via OLEDB or ODBC to the "replicators".
> All replicators communicate with the "sequencer", which determines the
> total order of all "SQL statements". The replicators then execute this
> total order against all connected databases, returning the result
> directly to the client.
>
>
> Jan
>
Thank you. I've read the paper, too, and was hoping other
people had investigated further. I will be talking to their
tech folks so I may have information if other people need it.
-- elein
>
>
>
>
> --
> #===================
====================
====================
===========#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me. #
> #===================
====================
=========== JanWieck- bwPqjjyvM7QAvxtiuMwx
3w@public.gmane.org #
>
|
|
|
|
|