Processing data object modifications in a networked storage system
Disclosed are various embodiments for triggering a processing of a data object stored in a bucket in a data store. A modification listener can determine that that the data object has been modified. The modification listener can trigger a processing of the data object by executable code associated with the data object.
1. A system, comprising:
a data store that stores data objects in one or more buckets associated with a user storage account; and
a cloud computing resource comprising one or more processors in communication with the data store, the one or more processors configured to at least:
determine that a data object stored in at least one of the one or more buckets in the data store has been modified;
generate a notification event in an instance when the data object in the data store has been modified; and
trigger a processing of the data object by executable code associated with the data object.
2. The system of claim 1 , wherein the data store is configured to be addressed by a locator.
3. The system of claim 1 , wherein the one or more processors are further configured to notify a listener associated with the data object.
4. The system of claim 3 , wherein the listener is further associated with at least one of: a function, a service, an application, or a system.
5. The system of claim 3 , wherein the one or more processors are further configured to identify, based at least in part on configuration data, an interface by which the listener is to be notified.
6. The system of claim 1 , wherein the one or more processors determine that the data object has been modified at least in part by determining that the data object has been updated, deleted, or moved.
7. The system of claim 1 , wherein the one or more processors are further configured to determine that at least one listener is associated with the data object.
8. The system of claim 1 , further comprising a browser-based configuration interface, a command-line interface, or an application programming interface through which a user can specify notification events and modifications to data objects stored in one or more buckets that will trigger such notification events.
9. A method, comprising:
Determining that a data object stored in a bucket in a data store has been modified;
generating a notification event in an instance when the data object in the data store has been modified; and
triggering a processing of the data object by executable code associated with the data object.
10. The method of claim 9 , wherein determining that the data object has been modified comprises determining that the data object has been updated, deleted, or moved.
11. The method of claim 9 , further comprising registering a modification listener as associated with determining that the data object has been modified.
12. The method of claim 9 , wherein the notification event corresponds to a particular data object type of the data object.
13. The method of claim 9 , further comprising notifying a listener associated with the data object.
14. The method of claim 13 , wherein the listener is further associated with at least one of: a function, a service, an application, or a system.
15. The method of claim 9 , further comprising triggering a subsequent processing by at least one of: a function, a service, an application, or a system associated with the data object.
16. A non-transitory computer-readable medium embodying instructions executable by a cloud computing resource comprising one or more processors, wherein when executed the instructions cause the one or more processors to at least:
determine that a data object stored in a bucket in a data store has been modified;
generate a notification event in an instance when the data object in the data store has been modified; and
trigger a processing of the data object by executable code associated with the data object.
17. The non-transitory computer-readable medium of claim 16 , wherein, when executed, the instructions further cause the one or more processors to at least trigger, based at least in part on configuration data specifying an interface, a subsequent processing by a listener associated with the data object.
18. The non-transitory computer-readable medium of claim 17 , wherein the listener is further associated with at least one of: a function, a service, an application, or a system.
19. The non-transitory computer-readable medium of claim 16 , wherein determining that the data object has been modified comprises determining that the data object has been updated, deleted, or moved.
20. The non-transitory computer-readable medium of claim 16 , wherein the notification event corresponds to a particular data object type of the data object.