1

Topic: Relational or NoSQL?

There are some companies which exchange the data about clients in the form of messages.
It is necessary to organize decentral distributed system of data storage about clients.
I will present it so, each company stores a copy of a DB and adds there necessarily a card of the dataful client or some cards, it is desirable that it was possible to add necessarily fields in a card or there was a possibility of a choice of an added field from earlier fixed additional fields. Also it would be desirable, that package adding of cards was supported.
By means of what it is the better and most convenient for organizing?

2

Re: Relational or NoSQL?

noob1111 wrote:

By means of what it is the better and most convenient for organizing?

Absolutely : a DB in this system not a key thing. Use that already is at these
The companies.

3

Re: Relational or NoSQL?

Dimitry Sibiryakov;
And what is key?

4

Re: Relational or NoSQL?

Dimitry Sibiryakov;
How forces of a DB to organize such system?

5

Re: Relational or NoSQL?

noob1111 wrote:

as forces of a DB to organize such system?

In any way.

6

Re: Relational or NoSQL?

noob1111 wrote:

There are some companies which exchange the data about clients in the form of messages.
It is necessary to organize decentral distributed system of data storage about clients...
It is desirable that it was possible to add necessarily fields in a card

here many questions without answers on which that or to advise it "bad shot"...
However, on , look in I will shift MongoDB + RabbitMQ

7

Re: Relational or NoSQL?

The grandfather;
There is a row of requirements
To organize the uniform protected automated platform for an information exchange between subjects according to available modern requirements and technologies.
The main requirement to decision structure - , that is absence of the selected "center" aggregating and controlling the assembled information.
Requirements to system.
Operation with basis
Possibility of data view to the user on demand (information search) should be implemented
Possibility of adding (change) of the data (basis addition) should be implemented
o adding of cards "on one"
o package adding
o at adding of the data possibility of identification before the created card should be provided
At adding of the data, possibility of the extension of cards additional fields should be implemented
o possibility of a choice of an added field from earlier fixed additional fields
o possibility of adding of new additional fields with fixing of the following information:
o the field identifier (it is unique in among all possible fields of a card)
o the field name (it is applied at creation GUI)

8

Re: Relational or NoSQL?

The grandfather;
There is a sentence to organize this all on  Ethereum networks, but personally it seems to me that it is quite possible to find an alternative more traditional variant

9

Re: Relational or NoSQL?

noob1111;
I saw the decision through web services
The circuit approximately the such:
Data Provider 1-> web-service 1 (provides data to DC)-> |
Data Provider 2-> web-service 2 (provides data to DC)-> |-> Data Collector-> data distribution web-service
Data Provider 2-> web-service 3 (provides data to DC)-> |

10

Re: Relational or NoSQL?

mini.weblab;
And it is possible more in detail as it works?

11

Re: Relational or NoSQL?

noob1111;
It is possible to look here. Plus still the documentation here quite good:
http://ec.europa.eu/eurostat/data/web-services

12

Re: Relational or NoSQL?

noob1111 wrote:

the Grandfather;
There is a sentence to organize this all on  Ethereum networks

From whom such sentence, from Google arrived? smile

13

Re: Relational or NoSQL?

noob1111 wrote:

the Main requirement to decision structure - , that is absence of the selected "center" aggregating and controlling the assembled information.

There are two methods of allocation of the data: a fragmentation (sharding) and replication. To you what it is necessary?

14

Re: Relational or NoSQL?

https://en.wikipedia.org/wiki/Multi-master_replication

15

Re: Relational or NoSQL?

skyANA;
Thanks, replication is necessary.
That is adjustment will look as is described here ?
And how to solve the conflict when two masters simultaneously add record?

16

Re: Relational or NoSQL?

http://tokarchuk.ru/2010/06/multi-master---mysql/

17

Re: Relational or NoSQL?

noob1111 wrote:

and how to solve the conflict when two masters simultaneously add record?

Most easier - organizational methods.

18

Re: Relational or NoSQL?

noob1111 wrote:

skyANA;
Thanks, replication is necessary.
That is adjustment will look as is described here ?
And how to solve the conflict when two masters simultaneously add record?

Under the link are enumerated a DBMS with multi-master-replikatsiej. If you selected MySQL esteem as conflicts there dare.

19

Re: Relational or NoSQL?

But judging by that you describe: "each company stores a copy of a DB and adds there necessarily a card of the dataful client or some cards", - I  would ask a question and when it is the different companies in one and  the moment add a card of the dataful same client.
The client that, simultaneously is in two places?

20

Re: Relational or NoSQL?

, I strongly would think before to take replication. Where at you these "companies" are allocated (in different cities, on different continents), quality of a communication channel, is how much possible a time delay in synchronization, is how much admissible duplication of "cards of the client" (there can be a duplication before cleaning procedure) both  and . Personally I would make itself, on easy services and message queues, but it strongly depends on your context.

21

Re: Relational or NoSQL?

The grandfather;
Generally the problem essence here in what, information transfer about clients (cards of clients) is conducted on normal electronic mail and the information . At such date transmission there is a row of problems such : mailing is led in an open type under the big list of electronic mailing addresses, in certain cases it leads to actuating of spams-filters on the side of receivers and to a nonreceipt them to the significant information, adding of new users in mailing is not supervised in any way + each receiver independently decides to store as the received information that complicates the further operation with the information. Number of participants of mailing 100 +
o Character of mailings the irregular;
It is necessary
o support of the protected data casting in the closed user group, is desirable that all messages reached addressees and by them have been processed lost-free
o tracing of adding of new participants in mailing
o support of the systematized, centralized storage of the received information on user side with possible subsequent handling and search in an array before the transferred information.
. it is necessary to organize the uniform protected automated platform for an information exchange between subjects with the systematized storage of messages.
It is necessary to pick up mechanisms for the optimal decision. I write the diploma

22

Re: Relational or NoSQL?

noob1111 wrote:

. it is necessary to organize the uniform protected automated platform
For an information exchange between subjects with the systematized storage of messages.
It is necessary to pick up mechanisms for the optimal decision.

All is already invented to you: use RSS.

23

Re: Relational or NoSQL?

Though is not present, RSS suits only the centralized mailing. So it is necessary for you P2P more likely
Or B2B.

24

Re: Relational or NoSQL?

skyANA;
And if companies 100 +? The multimaster replication approaches?

25

Re: Relational or NoSQL?

noob1111 wrote:

and if companies 100 +? The multimaster replication approaches?

The multimaster replication does not pull in the heterogeneous environment. It is necessary for you B2B and the coordination
Interchange format the data.