- Enables decoupling of applications for independent scaling.
- Enable the delivery of messages at least once, at low latency.
- Suitable for data arriving at high and unpredictable rates.
- A natural pairing with Cloud Dataflow for analyzing streaming data.
- Enables independent applications to send and receive messages.
- Holds onto data for up to seven days.
- Does not guarantee first in, first out.
- Can be the single ingest for all data points.
- Can dynamically rate limit.
- Enables users to throttle messages.
- Provides end-to-end reliability.
- Acknowledges at least one guaranteed delivery and receipt of each individual message.
- Messages are Published to a specific topic.
- Messages do not have to be received synchronously.
- Messages are completely encrypted.
- Applications can publish messages and one or more subscribers receive them.
- Decouples sender's transmission of the message from the receiver's receipt of the message.
- Message arrives at the subscriber where it is consumed.
- After a message is consumed, the publisher sends an acknowledgment to the subscription.
- When all deliveries are complete, messages are removed from the queue.
- No clusters to configure. Users simply pay for what they use.
- Uses two levels of indirection between the publisher and the subscriber.
- There is a small chance some messages might be delivered more than once.
- Offers on demand scalability to one million messages per second and beyond.
- PubSub builds on the same technology Google uses internally.