#Distributed Data Management

Distributed Data Management is a software architecture for creating, managing and accessing data on a remote computer.

By replies

Question

Tirthankar Bachhar · Aug 23, 2017

What is the benefit to keep separate database for Globals and Routines?

While creating namespaces, there is a provision for keeping the data, and code separately in database.

What I am looking for,

What are the benefit we can achieve by doing this?

Is there any documentation of article which might help understanding?

Thanks You!

#Databases #Distributed Data Management #Ensemble

0 9

0 1K

Question

Heikki Koivulehto · Oct 26, 2016

Shadowing between Caché 5.0.21 and 2016.2.0?

We are finally planning to migrate some ancient Caché applications that are run on Caché 5.0.21 to a new server with Caché 2016.2.0 or so.

I wonder if we could use Shadowing between those to keep the data on the new server up to date?

We would copy the Caché backup from the old environment to the new and do a RESTORE there and then start shadowing.

I know than 5.0.21 is no more officially supported by ISC.

#Caché #Compatibility #Databases #Distributed Data Management #Backup #Journaling

0 5

0 732

Question

Julius Kavay · Apr 22

What the heck is a "Reentrant request"?

I'm playing with %Net.DB.Iris and stumbled over a mystery

#Distributed Data Management #InterSystems IRIS

0 5

0 74

Question

Mark Bolinsky · May 19, 2016

Can Object Synchronization be used with more than two servers?

Consider a design where there could be three or four or more servers and there is a need to have these eventually consistent between them all (and not considering database mirroring here).

#Distributed Data Management #Object Data Model #Caché

1 2

0 395