Process multiple orders simultaneously and store in BD

Question

I’m dealing with a new problem because of some new challenges...

I developed a registration system and obviously in the future may have more than 100 registrations per day or even per hour or second. Thinking about it, I did a test on different pcs and did the registration at the same time using the two pcs, what happened was, the request of pc1 stored but the request of pc2 not.

I would like a help on how I can line up and then process orders if there are more than 1 at the same time...

Use jQuery to send the PHP form and the BD is mysql.

In PHP code is the normal code to insert data into a PDO DB

JS Code

    $.post("https://servidor/pasta/codigo.php", {
        nome: $nome,
        idade: $idade
}, function(dado){
      $("#msg").html("Inserido com sucesso");
})

Hugs and thanks in advance

Answer 1

What you said doesn’t make much sense, the server, depending on your setup, can "serve" hundreds/thousands of simultaneous requests. If you are using apache for example, the Directive MaxClients says the following:

The directive Maxclients arrow the amount of simultaneous requests that will be served. When this total is reached, the excess connection will enter a queue, the size of this queue can be set by the directive Listenbacklog.

The fact that two clients make a simultaneous request to the server is not a problem, in case this occurs, the server will create another process who will be responsible for the processing.

The question is, unless both scripts perform disk operations that require a lock (which is not your case), there is no timing technique that should be performed.

There are cases where it is necessary for transactional issues of the database to carry out special processing to prevent data from breaking integrity (which is also not the case following your example).

The problem in question is too broad, maybe it’s a problem in your test, who knows. The question I wanted to demonstrate in this text is almost with absolute certainty that it is not a synchronization problem unless your server is misconfigured.