You keep mentioning D1/Postgres, but it's not the same. In the scenario you bring up you mention web
You keep mentioning D1/Postgres, but it's not the same. In the scenario you bring up you mention webscockets where the client disconnected but you want the last updates they sent to be persisted guaranteed. Other databases, including D1/Postgres do not guarantee this at all.
Firstly, if the client disconnects, most probably at some point the connection will close too, regardless if the websocket server dies or not. If the client disconnected before their updates were acknowledged, then they are not guaranteed to be persisted and processed. This is not DO specific, it's general systems.
In general, if the client does not wait for ACK, then nothing is guaranteed. No matter the system. Unless you put the update in a queue and process it asynchronously in the background in the server.
Firstly, if the client disconnects, most probably at some point the connection will close too, regardless if the websocket server dies or not. If the client disconnected before their updates were acknowledged, then they are not guaranteed to be persisted and processed. This is not DO specific, it's general systems.
In general, if the client does not wait for ACK, then nothing is guaranteed. No matter the system. Unless you put the update in a queue and process it asynchronously in the background in the server.
