Micah Beck wrote:
>
> Wojtek Sylwestrza
>
> > When I hear service replication, I picture manually configuring remote
> > servers
> > (FTP, Web or other) and then mirroring the data from the origin server
> > onto them.
> >
> > The first part of this process is more or less manual, and one-time
> > only.
> > The second task is automated and periodical/continuous.
> >
> > Performing these both steps allow us to provide service on the replica,
> > but i'm not sure if it's necessary to have a special terminology for
> > this.
> >
> > Do I understand service replication right, or does it have a broader
> > sense ?
>
> I intend "service replication" to mean any situation where a service is
> available in more than one place. Manually set up mirroring is one example,
>
Sorry, I was not clear.
What I meant was that the whole process of "service
replication" as I understood it, consists of two parts:
1. configuring the server on replica to provide the copied contents.
whether this is an FTP, HTTP or some more complex database server,
I cannot imagine doing this other way than manually
2. configuring the mirroring process (a mirror scripts, rsync or such)
to update the contents of the replica periodically or continuously
(this obviously is a manual task, but that's not the point)
and then running it automatically.
So again, my understanding was, that task 2 is called 'mirroring'
while if we want to name both 1+2 together,
this would be 'service replication'.
And 'service replication' does not necessarily have to involve
mirroring,
the particular technique used in step 2. can be caching or something
else.
I think this also fits with your definition.
--w
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST