c# - .NET or MySql or other solution for millions of lookups a day (to stop duplicates) -


I have a client / server architecture that is written in the network, where hundreds of customers send data to a server. Each item has an ID and it is possible to send the same ID multiple times to different customers.

The IDs are long and the server needs to know whether something has already been received with an ID. Every day, with 10,000,000 duplicates, the server will get 10,000,000 ids every time it receives an ID, it will be necessary to look for any kind of information to see whether it is already related or not.

My current ideas for the solution are:

  • With a background thread, the id's memory dictionary contains more than 3 days after being in the dictionary for someone Also to remove items

  • MySQL database with an indexed column for ISC and a column for the entry date.

    The issue I raise can be a speed like the Mykkil database, because I have to ask ~ 10,000,000 questions in a day. I am not going to use fancy hardware for this particular issue (typical development system) and I do not want to tax it at 100%. The problem with memory solutions is that there will be trouble writing the background worker (concurrency) and all this has probably been lost in the accident.

    MySQL is not definitive about the part - usually with the HW that you use Good scales are ...

    Use only one for the dictionary part - these threads are safe and really fast because most of the operations are lock-free.

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -