Help in designing the high-level architecture of a software module

I need help in the design of an object.

The object is a list of records.
Records can be added, removed or modified by clients (using a Web API or another means).
The clients should be notified of any new update to Refresh their interface (Listeners?)
Some concurrency handling is needed.
1-If an Item is deleted by client A, and shortly afterwards client B tries to modify it, nothing should happen
2-Ideally, an action should be refused if the timestamp of its record is earlier to the record current timestamp on the server.

Also, I need the object status to be persisted in a database, so that is a crash happens the system can reinitialize its state.
Actually, I dont need the object in memory, but I am not sure if using database triggers is appropriate in such case.
About the recuiter
Member since Mar 14, 2020
Kamlesh Savaliy
from Abruzzi, Italy

---

---

Offer to work on this project closes in 77 days!
Are you interested in this Opportunity?

Looking for help? Checkout our video tutorial
How to search and apply for jobs

How to apply? Do you have more questions about the Job?
See frequently asked questions