Organizing and responding to events in a decentralized system (such as with microservices or IoT) can be a challenge. In this course, you will learn how to use Google Cloud Pub/Sub to create a reliable, asynchronous, messaging service for any scale.
- Understand what Cloud Pub/Sub is
- How to send and receive messages
- What the typical use cases are
- How to get started
- GCP Developers
- GCP Data Engineers
- Anyone preparing for a Google Cloud certification (such as the Professional Data Engineer exam)
- Access to a Google Cloud Platform account is recommended
At this point, you should have a pretty good understanding of what Cloud Pub/Sub is and what it can do. Let's do a quick recap of everything that was covered.
First, you learned that Google Cloud Pub/Sub is a scalable message queuing service. It provides reliable, asynchronous messaging between different apps and services. It is also very flexible and supports one-to-many communication, many-to-one, and many-to-many.
Second, you learned exactly how Pub/Sub accomplished this by using messages, topics, publishers, and subscribers. Messages contain the actual data that is going to be sent. The message data typically contains information about some sort of a change event. Topics represent the different categories of messages available. Messages are added to and read from topics. Topics store the messages, and they allow you to control what types of messages you will receive. Publishers are applications that add messages to a topic. Each topic can have one or many publishers. Subscribers are applications that read the messages from a topic. Each subscriber needs one subscription per topic. Subscribers can share subscriptions or each have their own. A shared subscription means that a message will only be sent to one subscriber at random. Subscriptions can be either "pull" or "push." A "pull" subscription means the subscriber will be manually pulling for all new messages. A "push" subscription means the topic notifies the subscriber every time it receives a new message.
Finally, you learned that Pub/Sub consists of two different services, Pub/Sub and Pub/Sub Lite. Pub/Sub is more expensive, but it has higher reliability and a larger set of integrations. It also does not require any manual provisioning, and you only have to pay for the capacity that you use. Pub/Sub Lite can be much less expensive, but it involves additional operational work, and it provides lower availability. For most scenarios, Pub/Sub will generally be your best option.
Well, that's all I have for you today. Remember to give this course a rating, and if you have any questions or comments, please let us know. Thanks for watching, and make sure to check out our many other courses on Cloud Academy!
Daniel began his career as a Software Engineer, focusing mostly on web and mobile development. After twenty years of dealing with insufficient training and fragmented documentation, he decided to use his extensive experience to help the next generation of engineers.
Daniel has spent his most recent years designing and running technical classes for both Amazon and Microsoft. Today at Cloud Academy, he is working on building out an extensive Google Cloud training library.
When he isn’t working or tinkering in his home lab, Daniel enjoys BBQing, target shooting, and watching classic movies.