Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread replication
Sun, Jun 15 2008 4:37 AMPermanent Link

"Harry de Boer"
LS,

I'm still wondering about the replication which seems to be a 'hype' for EDB
2. What is it really for. Can someone explain to me in what situations it is
usefull. What we have is a middleware server that points to a central
database so all users have access to the updated data via the middleware
server. For backup you can use several methods. So, what are the benefits?

I'd really appreaciate some info on 'live' examples.

Regards, Harry

Sun, Jun 15 2008 5:19 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Harry,

<< I'm still wondering about the replication which seems to be a 'hype' for
EDB 2. What is it really for. Can someone explain to me in what situations
it is usefull. What we have is a middleware server that points to a central
database so all users have access to the updated data via the middleware
server. For backup you can use several methods. So, what are the benefits?
>>

If you're already using a middleware solution, then you don't have as much a
need for it as someone that isn't using a middleware solution.  However, the
native EDB replication offers these features that may not be in your
middleware product:

- It's designed for replicating servers also (including hot backup)
- It's can handle replicating data very infrequently, or very frequently
- Can do push or pull synchronization
- Database updates can be distributed via non-traditional methods such as
via email
- It can also replicate non-database data and files

How often are your users synchronizing with the middleware server ?

<< I'd really appreaciate some info on 'live' examples. >>

I'll be posting a technical article that gives a replication example on
Monday.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sun, Jun 15 2008 5:46 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Harry


Not a live example, and might never be so with my app since I use f/s not c/s but think of this scenario:

Nice big c/s app running over the internet so a fair bit of latency involved. Some data is fairly static but is used for lookup/display and results in the app being very chatty thus slowing it down. Replicate the lookup tables and use locally and you'll have a much faster app.

or

You have a mobile workforce who can't log on to the internet all the time but need access to the data (modern laptops with 250Gb disk etc) so store locally and update the central and their database when they can log in.

Personally I think its one of those things where if you have a need for it then it will make your life much easier by comparison with rolling your own otherwise you'll be left thinking what's the fuss.

Roy Lambert
Sun, Jun 15 2008 8:21 AMPermanent Link

Jan Ferguson

Data Software Solutions, Inc.

Team Elevate Team Elevate

Harry,

In the case of any application which operates 24/7 and must have a
database which is "ready-to-go". For example, a police department is
using Computer Aided Dispatch (CAD) which contains ALL their calls for
service and historical information on an address which could be needed
for officer safety (i.e., a nut job who likes to attack officers.) The
CAD server (Server 1) goes down. Luckily the data from Server 1 has
been replicated to another server (Server 2) and is "ready-to-go". A
transfer utility senses Server 1 is down and automatically makes Server
2 the "active" data server or the change is made in seconds via a
configuration file.

That's a live example which I am involved with everyday (not the going
down of the server portion but rather the replication of the data.) No
muss or fuss with middleware, just simple data replication. I'm now
glad that I can offer this type of functionality in my own products.

--
Regards,
Jan Ferguson [Team Elevate]


Harry de Boer wrote:

<<I'd really appreaciate some info on 'live' examples.
Image