An asynchronous version of DatastoreService. All methods return immediately and provide
Futures as their return values.
The key difference between implementations of AsyncDatastoreService and
implementations of DatastoreService is that async implementations do not perform implicit
transaction management. The reason is that implicit transaction management requires automatic
commits of some transactions, and without some sort of callback mechanism there is no way to
determine that a put/get/delete that has been implicitly enrolled in a transaction is complete
and therefore ready to be committed. See ImplicitTransactionManagementPolicy for more
information.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["AsyncDatastoreService is an asynchronous version of DatastoreService, providing Futures as return values for all methods, allowing for immediate returns."],["Unlike DatastoreService, AsyncDatastoreService does not perform implicit transaction management because it lacks a callback mechanism to determine when transactions are ready to be committed."],["All methods of AsyncDatastoreService immediately return a Future object which allows for non blocking code that can be run concurrently."],["AsyncDatastoreService provides various methods for data manipulation, including allocating IDs, beginning transactions, and deleting, getting, and putting entities, with some methods having transaction management versions."],["AsyncDatastoreService implements BaseDatastoreService."]]],[]]
