One possible solution could be to return the status of the order creation in the primary database only after receiving acknowledgements from all of its replicas. By doing so, we can ensure that the data remains consistent across all database nodes when an order is created and communicated to the client.
One possible solution could be to return the status of the order creation in the primary database only after receiving acknowledgements from all of its replicas. By doing so, we can ensure that the data remains consistent across all database nodes when an order is created and communicated to the client.
Wouldn’t this increase the latency of the order creation API?