Re: Relational or NoSQL?
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
We for email mailings use sheaf ActiveMQ + MailBee