![]() All this picture metadata is stored in Cloud Firestore. It calls the Vision API to assign labels to the picture, identify the dominant colors, and check if it’s a picture safe to show publicly. ![]() A Cloud Function (Image analysis) reacts to file creation events.Those pictures are stored in a Google Cloud Storage bucket, which triggers file creation and deletion events, propagated through mechanisms such as Pub/Sub and Eventarc. Users upload pictures on an App Engine web frontend.As new services were added over time, a loosely-coupled, event-driven architecture naturally emerged, as shown in this architecture diagram: The Pic-a-Daily application evolved progressively. All the code is open source and available in a GitHub repository. The workshop consists of codelabs that you can complete at your own pace. ![]() We also created a hands-on workshop to build the application, and slides with explanations of the technologies used. ![]() Into the mix, we’ve thrown a pinch of Pub/Sub for interservice communication, a zest of Firestore for storing picture metadata, and a touch of machine learning for a little bit of magic. Over the past year, we ( Mete and Guillaume) have developed a picture sharing application, named Pic-a-Daily, to showcase Google Cloud serverless technologies such as Cloud Functions, App Engine, and Cloud Run. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |