> choose whether or not they want to accept an order."
If the app shows clearly what needs to be done (shop, order list, miles driven), and the pay the worker will earn, and asks if they want to accept, then IMO that's fine.
The business can set those offers however they like, even using a random number generator if they want, and IMO it's morally fine.
What if there's discrimination built in to the system? Maybe a business is willing to pay white people more, or women less. They can do that while still following your framework. Is that moral?
At launch, they limited the number of affected tuples to 10000, including tuples in secondary indexes. They recently changed this limit to:
> A transaction cannot modify more than 3,000 rows. The number of secondary indexes does not influence this number. This limit applies to all DML statements (INSERT, UPDATE, DELETE).
There are a lot of other (IMO prohibitive) restrictions listed in their docs.
https://docs.aws.amazon.com/aurora-dsql/latest/userguide/wor...