Postgres
>just use SQLite
what the fuck for? I'm build servers, not single-writer databases.
>it's simpler
nigga if you struggle to work with Postgres then are going to have a horrible time trying to build complex software.
>>105799306
this, conflicts are handled with transactions. make sure to use the correct isolation level (I default to serializable because it makes reasoning about things dead simple, which is the most important attribute when designing concurrent behaviors).
also make sure you have retry logic figured out.
also consider leaving a transaction open as a human makes a decisions based on the state of some data. if this takes too long, then you might need to re-consult data to ensure it has not changed.