1

Topic: Data storage from several processes

, help to organize a read and write of the data  from several processes. There are some processes, they read the data from one source, and can write there the data and all simultaneously. It is necessary to make something of database type that all processes had to it access. But the database should not be installed, type as mysql, mssql, i.e. the user launches ten processes and all is silent, without setting works. Well as a variant to launch one process of type of service which will work with a database, well for example sqlite (?), and all remaining processes will send requests about a read or write given to this process. How all is correct it to organize? Can eat what alternative variants? A C programming language ++ at the worst C#.

2

Re: Data storage from several processes

Hello, vladimir.romin, you wrote: VR> Drugi, help to organize a read and write of the data  from several processes. VR> there are some processes, they read the data from one source, and can write there the data and all simultaneously. It is necessary to make something of database type that all processes had to it access. VR> but the database should not be installed, type as mysql, mssql, i.e. the user launches ten processes and all is silent, without setting works. VR> well as a variant to launch one process of type of service which will work with a database, well for example sqlite (?) And all remaining processes will send requests about a read or write given to this process. sqlite it is normal. Anything to install , only  with itself to drag. Service is not necessary,  at reversal to one sklajt-BD from different processes itself  all perfectly resolves (an engine itself organizes all necessary locks for synchronization of accesses). Allows to have many competitive readers and one writer. If records it is necessary to do that in one transaction much. Problems (in the form of waiting by the writer removal of lock from other writer) can begin if it is a lot of competitive writers, if transactions short and are not intersected almost - all  will be.

3

Re: Data storage from several processes

Hello, vladimir.romin, you wrote: VR> Drugi, help to organize a read and write of the data  from several processes. VR> there are some processes, they read the data from one source, and can write there the data and all simultaneously. It is necessary to make something of database type that all processes had to it access. VR> but the database should not be installed, type as mysql, mssql, i.e. the user launches ten processes and all is silent, without setting works. VR> well as a variant to launch one process of type of service which will work with a database, well for example sqlite (?) And all remaining processes will send requests about a read or write given to this process. VR> as all is correct it to organize? Can eat what alternative variants? A C programming language ++ at the worst C#. I join judgement about sqlite, for at the most such architecture. It is possible to have and more than one writer (or to optimize record) by means of WAL.

4

Re: Data storage from several processes

Hello, vladimir.romin, you wrote: Besides sqlite, is still MSSQL Compact and firebird embedded. By possibilities they will be more abruptly.

5

Re: Data storage from several processes

Hello, vladimir.romin, you wrote: VR> Well as a variant to launch one process of type of service, which will work with a database, well for example sqlite (?), and all remaining processes will send requests about a read or write given to this process. VR> as all is correct it to organize? Can eat what alternative variants? A C programming language ++ at the worst C#. In general in a question the answer also is specified. Or to take sqlite if it is necessary given to store in a database type, or if suddenly constant data storage is not necessary, and the operative data wcf service which will work with all remaining processes and to process and store the small data operatively and, probably are necessary only, if needed  them sometimes in a file in the necessary format (for example at operation end) and as sometimes to deserialise.