google pub/sub有没有像kafka那样的partition的概念？
Does google pub/sub have concept of partition like kafka?
如果 n 个订阅者在 google pub/sub 中共享一个主题的 1 个订阅，分区策略是什么？
是循环赛吗？或者如果没有重新平衡，每个订阅者是否保证有一组密钥？
您可以针对同一主题创建多个订阅，其中 filter on the message attributes 仅订阅 select 个消息子集。
您不能根据同一订阅的订阅者设置分区。
PubSub lite 似乎有分区的概念。
https://cloud.google.com/pubsub/lite/docs/topics#provisioning_capacity
https://cloud.google.com/pubsub/lite/docs/subscribing#receiving_messages
To receive messages from a Lite subscription, request messages from the Lite subscription. The client library automatically connects to the partitions in the Lite topic attached to the Lite subscription. If more than one subscriber client is instantiated, messages will be distributed across all clients. The number of partitions in the topic determines the maximum number of subscriber clients that can simultaneously connect to a subscription.
如果 n 个订阅者在 google pub/sub 中共享一个主题的 1 个订阅，分区策略是什么？
是循环赛吗？或者如果没有重新平衡，每个订阅者是否保证有一组密钥？
您可以针对同一主题创建多个订阅，其中 filter on the message attributes 仅订阅 select 个消息子集。
您不能根据同一订阅的订阅者设置分区。
PubSub lite 似乎有分区的概念。
https://cloud.google.com/pubsub/lite/docs/topics#provisioning_capacity
https://cloud.google.com/pubsub/lite/docs/subscribing#receiving_messages
To receive messages from a Lite subscription, request messages from the Lite subscription. The client library automatically connects to the partitions in the Lite topic attached to the Lite subscription. If more than one subscriber client is instantiated, messages will be distributed across all clients. The number of partitions in the topic determines the maximum number of subscriber clients that can simultaneously connect to a subscription.