Large volume report operations, how best to replicate transactional data
We are overhauling a legacy accounting app that has some large reports. One concern that has been raised is due to the transactional nature of the data, if we start a long running report how do we ensure the data is not modified before we get around to processing it?
Is there a term for data being written not being immediately available to be read?
Here is a problem I’ve repeatedly observed over the years:
Is there a term for data being written not being immediately available to be read?
Here is a problem I’ve repeatedly observed over the years:
how to decide when to use database replication vs. custom REST applications vs. message brokers (pub / sub)
We have a distributed solution that’s currently under design. There are a few points of integration where some application needs data from someone else and vice versa. We could solve by either writing REST interfaces and provide CRUD features so that apps can share data between themselves. Or we can use something like nanomsg or zeroMQ to send messages back and forth.
how to decide when to use database replication vs. custom REST applications vs. message brokers (pub / sub)
We have a distributed solution that’s currently under design. There are a few points of integration where some application needs data from someone else and vice versa. We could solve by either writing REST interfaces and provide CRUD features so that apps can share data between themselves. Or we can use something like nanomsg or zeroMQ to send messages back and forth.
how to decide when to use database replication vs. custom REST applications vs. message brokers (pub / sub)
We have a distributed solution that’s currently under design. There are a few points of integration where some application needs data from someone else and vice versa. We could solve by either writing REST interfaces and provide CRUD features so that apps can share data between themselves. Or we can use something like nanomsg or zeroMQ to send messages back and forth.
how to decide when to use database replication vs. custom REST applications vs. message brokers (pub / sub)
We have a distributed solution that’s currently under design. There are a few points of integration where some application needs data from someone else and vice versa. We could solve by either writing REST interfaces and provide CRUD features so that apps can share data between themselves. Or we can use something like nanomsg or zeroMQ to send messages back and forth.
how to decide when to use database replication vs. custom REST applications vs. message brokers (pub / sub)
We have a distributed solution that’s currently under design. There are a few points of integration where some application needs data from someone else and vice versa. We could solve by either writing REST interfaces and provide CRUD features so that apps can share data between themselves. Or we can use something like nanomsg or zeroMQ to send messages back and forth.
Sequencing distributed tasks with a distributed DB
Is there a general term (or terms) for this pattern, so that I can read about how to solve it? Unfortunately I don’t even know what the right terminology is so I’ve had a heck of a time doing research on Google/SO/Programmers.SE.
Using ESB for database synchronisation / replication
We’re starting to look at implementing an ESB / Microservices architecture. I (think) I know about the concepts, but there’s one thing I don’t seem to be able to get a good idea about: data replication / synchronisation.