This is as any other database really. Ideally, you should not be doing remote calls within your tran
This is as any other database really. Ideally, you should not be doing remote calls within your transactions, since it slows down everything. Do your remote call to fetch something, and then start a transaction to do your writes. If the server crashes the writes won't be partially done.
How is this use-case different than any traditional application running on a server and crashing in the middle of your transaction? The database transactions only guarantee consistency within the database, not with the remote calls you make, so retries and all that depends entirely on what the application is doing.
We cannot blindly retry database queries for you since we don't know if it's safe to do so. You are the one knowing that.
How is this use-case different than any traditional application running on a server and crashing in the middle of your transaction? The database transactions only guarantee consistency within the database, not with the remote calls you make, so retries and all that depends entirely on what the application is doing.
We cannot blindly retry database queries for you since we don't know if it's safe to do so. You are the one knowing that.
