Answer the question
In order to leave comments, you need to log in
Branch network database consolidation using PostgreSQL. How?
There is a network of a couple of dozen branches.
Each branch has one or two Windows machines that do simple inserts into the database in the form of "time - device - value".
The task arose to consolidate these statistical data at the central office for analysis. There is no stable communication channel, so the data must first be transmitted to the central office.
So far, the structure is seen as a central slave database, with the number of schemas equal to the number of branches, hosted on linux or windows.
Each branch merges changes to its public schema (or the central server picks up the branch's public) into its corresponding personal schema in the central slave base. At the same time, the possibility of access from one branch to the schemes of another should be excluded.
Is it possible without the invention of the bicycle?
Answer the question
In order to leave comments, you need to log in
It is worth reading about patterns, as well as Event Sourcing, etc.
It's probably better to make one central database and merge data from the branch once in a while.
In general, everything depends very much on the task.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question