Many workflows, such as the previously demonstrated one, are inherently event-driven. They revolve around one component writing output into Cloud Storage, and other components taking actions as a result. Being event-driven, Cloud Functions are often a natural fit for workflows involving Cloud Storage. As we covered in Chapter 6, Google Cloud Functions, Cloud Functions have first-class support for Cloud Storage triggers.
Building on our last example, we can leverage Cloud Functions to take some action when a user uploads images. There are many such actions we might want to take, such as generating thumbnails, compression, indexing the images into other systems, or performing some form of analysis. Here, ...