KATSUTOMO.GOUDO | 2023-02-07 07:05:22 UTC | #1
HI. I am developing an application using Notification APIs, but I have the following questions
Question.1 What does the limits app.user.channels.max (20) mean? A. If you are using the same OAuth client user from multiple programs, the total limit is 20. B. Limit of 20 per token created based on the OAuth client user (Even if you use the same OAuth client user, you can create more than 20 channels at the same time by creating a new token) C. Other
Question.2 Is there a way to estimate the limits notification.rate.per.minute, websocket.rate.per.second ? (The amount of traffic and data actually generated will vary depending on the topic, etc.) Do you have any information or techniques for estimating the amount of traffic and data used?
Question.3 A confirmation about Combine related topics. Currently, we simply subscribe to v2.users.{id}.conversations and v2.users.{id}.activity per user, which limits us to 500 users per channel (1000 / 2 = 500). Using this Combine format format you can write 3 topics in 200 characters or less (A combined topic can contain up to 200 characters. Limitation) It has been tested in the development environment. I'm assuming that this will allow me to subscribe to 3 * 1000 = 3000 topics in one channel, thereby serving 3000 / 2 = 1500 users, is this correct?
John_Carnell | 2023-02-08 15:01:40 UTC | #2
Hi Ktsuomo,
Question #1 - The app.user.channels.max limit means that you are limited to 20 channels per user and app. Remember that you can use the notification service with a client credential grant or a user-context-based token. In the case of a user (regardless of the app), you are limited to 20 channels max. In terms of a client-credential grant, it is 20 per token.
Question #2 - Not sure because so much of that is dependent on the specific traffic patterns of the customer
Question #3 - Per the documentation the whole purpose of the combined topic is to allow you to subscribe to multiple topics as a single topic, thereby freeing up additional topic subscriptions under the 1000 connection limit. You still have a 1000-topic subscription but this does allow you to aggregate messages coming from, for instance, the same user.
One thing I would ask you to consider with the notification service is the type of application you are trying to build. Unless you are building a client-side-only application, our AWS EventBridge notification is a better and more stable solution for doing message-driven development. It eliminates much of the complexity associated with processing large amounts of data.
If you are building a UI-based solution then the notification service often is appropriate, but event-bridge is easier to use for back-end integrations.
Thanks, John Carnell Director, Developer Engagement
KATSUTOMO.GOUDO | 2023-02-10 03:27:23 UTC | #3
Hi John
Thank you for answering. OK.Also consider AWS EventBridge.
Regards Katsutomo
John_Carnell | 2023-02-10 14:08:12 UTC | #4
This post was migrated from the old Developer Forum.
ref: 18308