Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Serverless Computing with Google Cloud

You're reading from   Hands-On Serverless Computing with Google Cloud Build, deploy, and containerize apps using Cloud Functions, Cloud Run, and cloud-native technologies

Arrow left icon
Product type Paperback
Published in Feb 2020
Publisher Packt
ISBN-13 9781838827991
Length 320 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Richard Rose Richard Rose
Author Profile Icon Richard Rose
Richard Rose
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Section 1: App Engine
2. Introducing App Engine FREE CHAPTER 3. Developing with App Engine 4. Section 2: Google Cloud Functions
5. Introducing Lightweight Functions 6. Developing Cloud Functions 7. Exploring Functions as a Service 8. Cloud Functions Labs 9. Section 3: Google Cloud Run
10. Introducing Cloud Run 11. Developing with Cloud Run 12. Developing with Cloud Run for Anthos 13. Cloud Run Labs 14. Section 4: Building a Serverless Workload
15. Building a PDF Conversion Service 16. Consuming Third-Party Data via a REST API 17. Assessments 18. Other Books You May Enjoy

Email/SMS communication

For the sake of brevity in our proof of concept, the email and SMS services will utilize a similar code base to demonstrate how background services can be designed within Google Cloud. While these components are meant to provide isolated services, in our example, we will use common code to demonstrate their functionality. In a real-world situation, the communication component presents an opportunity for a common code base to be replicated/extended for different solutions (for example, email, bots, SMSes, pagers, and more).

The Cloud Pub/Sub topic we previously created pushes the data to be consumed by the communication components. In this instance, the lab report data object represents a JSON file that is used to communicate lab results:


It is worth pointing out that we have not actually referenced the data passed in the lab report, nor do we know the...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime