publish-subscribe

问题 What are the pros and cons of each? Please advice when to use one and not the other. 回答1: Data storage Pub/Sub is a Publisher/Subscriber platform, it's not data storage. Published messages evaporate, regardless if there was any subscriber. In Redis Streams, stream is a data type, a data structure on its own right. Messages or entries are stored in memory and stay there until commanded to be deleted. Sync/Async communication Pub/Sub is synchronous communication. All parties need to be active

问题 What is a best data format for publishing and consuming to/from Pub-Sub? I am looking at Avro message format due to it's binary format. Usecases are there would be real time Microservice applications publishing Avro messages to pub-sub. Given that avro message is best suited when batching up messages(along with a schema attached with the binary message) and then publishing the messages, would that be a better suitable format for this usecase involving microservice? 回答1: Google Cloud

问题 I am testing out a very basic Pub/Sub subscription. I have the push endpoint set to an App I have deployed through a Python Flex service in App Engine. The service is in a project with Identity-Aware Proxy enabled. The IAP is configured to allow through users authenticated with our domain. I do not see any of the push requests being processed by my app. I turned off the IAP protection and then I see that the requests are processed. I turn it back on and they are no longer processed. I had

问题 I am testing out a very basic Pub/Sub subscription. I have the push endpoint set to an App I have deployed through a Python Flex service in App Engine. The service is in a project with Identity-Aware Proxy enabled. The IAP is configured to allow through users authenticated with our domain. I do not see any of the push requests being processed by my app. I turned off the IAP protection and then I see that the requests are processed. I turn it back on and they are no longer processed. I had

问题 I've have multiple subscribers who are subscribed to the same Redis channel. Does Redis guarantee that all subscribers get all the messages that are pushed into the channel after the subscribers subscribes for the channel ? 回答1: From redis docs Messages sent by other clients to these channels will be pushed by Redis to all the subscribed clients. I guess thats a Yes to your question. 来源： https://stackoverflow.com/questions/17255314/redis-multiple-subscribers

问题 I've have multiple subscribers who are subscribed to the same Redis channel. Does Redis guarantee that all subscribers get all the messages that are pushed into the channel after the subscribers subscribes for the channel ? 回答1: From redis docs Messages sent by other clients to these channels will be pushed by Redis to all the subscribed clients. I guess thats a Yes to your question. 来源： https://stackoverflow.com/questions/17255314/redis-multiple-subscribers

问题 I'm asking your sugegstions about an "architectural" scenario: I'd looking for a simplest publish/subscribe architecture to let talk two decoupled servers over on internet, sharing "sparse" but "real-time" messages/events. Let me explain: The PUBLISHER: Is a server (http://www.server.com) that generate some sort of events (by example events==ORDERS data on a e-commerce website). SUBSCRIBERS (one or more): Are "clients" that can subscribe to receive ORDERS events (http://www.client.com). In

问题 I am exploring redis to do pub/sub. I wanted to write a script that uses redis-cli to subscribe to a channel and dump whatever is published to a file. What I notice however is that redis-cli subscripe channel > output does not quite work. I'd appreciate any help very much. Regards, Kashyap 回答1: This is because there is no automatic flush of stdout when redis-cli displays the messages associated to the subscription. So the last messages before stopping redis-cli do not appear in the output

问题 i'm trying to implement pub sub pattern using grpc but i'm confusing a bit about how to do it properly. my proto: rpc call (google.protobuf.Empty) returns (stream Data); client: asynStub.call(Empty.getDefaultInstance(), new StreamObserver<Data>() { @Override public void onNext(Data value) { // process a data @Override public void onError(Throwable t) { } @Override public void onCompleted() { } }); } catch (StatusRuntimeException e) { LOG.warn("RPC failed: {}", e.getStatus()); } Thread

问题 i'm trying to implement pub sub pattern using grpc but i'm confusing a bit about how to do it properly. my proto: rpc call (google.protobuf.Empty) returns (stream Data); client: asynStub.call(Empty.getDefaultInstance(), new StreamObserver<Data>() { @Override public void onNext(Data value) { // process a data @Override public void onError(Throwable t) { } @Override public void onCompleted() { } }); } catch (StatusRuntimeException e) { LOG.warn("RPC failed: {}", e.getStatus()); } Thread