Communications Firmware
For the wifi communication between the client (controller) and the server websockets are chosen as the protocol. Since they only have one initial handshake and the port is left open, the latency is very low.
Inside the ESP microcontroller, we can exploit the rtos possibilities running multiple tasks, one that communicates with the controller (client) and another that sets and reads the sensors.
Said tasks run asynchronously, and to avoid the pain of async message buffers the input and output data is written in an array fixed in memory (with the proper semaphores to avoid corruption due to multiple access).
Is important to know that uri driving task shoud interact with the database at least at two times the frequency that the client does. That shouldn't be a problem but it must be kept in mind.