how to SNS Topic handle more than 10 million subscriptions.
Request increase the limit.
is any other option to handle this scenario.
Topic: MyAPPNOTIFICATION
Reached 9.9 Million subscriptions.
The 2014 Amazon SNS Update – Large Topics and MPNS Authenticated Mode blog post from AWS says:
Today we are lifting the limit of 10,000 subscriptions per SNS topic; you can now create as many as you need and no longer need to partition large subscription lists across multiple topics. This has been a frequent request from AWS customers that use SNS to build news and media sharing applications.
There is an administrative limit of 10 million subscriptions per topic, but we’ll happily raise it if you expect to have more subscribers for a single topic. Fill out the Contact Us form, select SNS, and we’ll take good care of you!
Related
Introduction
So from the official firebase docs. It states there that:
The frequency of new subscriptions is rate-limited per project. If you send too many subscription requests in a short period of time, FCM servers will respond with a 429 RESOURCE_EXHAUSTED ("quota exceeded") response. Retry with exponential backoff.
The topic subscription add/remove rate is limited to 3,000 QPS per project.
qps = queries per second.
Now here's the thing. It says "per project". What if an app gets very popular and thousands of users open the app at the same time then click a button that subscribes to a topic or unsubscribe?
Wouldn't hitting the rate limit 3000 queries per second highly possible?
Here's my real question
Does firebase_messaging's subscribeToTopic(..) and unsubscribeFromTopic(..) methods automatically handle retries? (referring to "Retry with exponential backoff" above)
If not, then how would a very popular app handle topic subscriptions from a massive number of users?
Because the plugin does not provide any documentation about this.
Coming from a different platform (Android) for your question on subscribeToTopic() retry?, but possibly both function similarly. On Android it returns a Task where in Flutter it returns Future (Task = Future for Flutter if I understood that correctly), which I presume is a hint that Google gave the responsibility for the retries to the developers.
I'm not sure what your looking for as an answer. The correct way is to implement an exponential backoff as mentioned in the docs. Depending on your use-case, different strategies can be implemented.
e.g. forced subscription -- like a general topic, that runs every app start is easy. One-off subscriptions, you might need some verifications i.e. a way to check if the user actually finished subscribing, retry if not.
Does anyone know how many concurrent requests per second can be made to sabre developer bargain finder Max API?
I have searched everywhere and all I can find is contact your rep to have it increased.
We had the setup of 50 Sessions included but it was no hard limit. Also we were able to extend it to 150 without any costs. There is as far as i know no limit on concurrent requests but depending on what calls you make, you should have your "look to book ratio" (usually 500:1) in mind.
I believe they are usually sold in bundles of 50 sessions per EPR but can be increased. I do not believe there is any way of viewing that information about a given EPR in any kind of tool, so your rep is the best place to go for that kind of information. Pricing depends on all sorts of contractual items, I believe.
There is a certain limit associated with the number of concurrent requests for the API. If the same gets exceeded, you would get the following error :- USG_CONNECTOR_IS_BUSY. This means that the maximum number of concurrent requests for the API has been exceeded. Please contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API. In this case, wait at least 500 milliseconds and resend the request.
The allocations are usually increased in bundles of 50. Your Sabre account manager would be the best person who can provide specific details.
#PCM7,
There is no specific limit, as this depends on the commercial agreement between the travel agency and Saber, as the token generated for the BFM is managed directly at SABRE.
In the agency where I work we have several tourism companies and with that each one has a specific amount of TPS for BFM.
This information will be obtained directly from the SABER account executive for the travel agency in question.
https://developer.sabre.com/docs/soap_apis/air/search/bargain_finder_max
I'm using Amazon SNS for sending Text Message blasts to subscribers on my site. I would like to be able to have a different short code to send from, assigned if possible to one of my User accounts which have already been created and which have their own Key and Secret for use with the SNS API.
Where do I go in the AWS Console to set this up? Is this possible or not?
It is possible. Take a look at the AWS docs. You ultimately need to create an SNS Limit Increase case with Amazon support. But make sure you follow the SMS Pricing doc because it's not cheap or quick:
Amazon SNS now supports dedicated short codes for the US destinations.
Each dedicated short code is $995 per month. You are billed for your
dedicated short code addresses at the end of each month along with any
other Amazon SNS text message sending charges you incur.
The United States Short Codes will incur a one-time setup fee of $650.
Carrier approval may take 8-12 weeks (or longer), and your short code
may not be fully live with all US carriers during this period.
To request a dedicated short code, open a dedicated short code limit
increase case in Support Centre.
I am using google cloud pub/sub for receiving the push notifications of any gmail user by setting a watch on the concerned users mailbox. I am able to do that. I am creating a one topic per user in my google console project and also creating one subscription per topic. As per my knowledge we cannot make more than 10,000 topics and subscriptions in one project(GCP). My question is that can we increase this limit. I want to increase it to 100k or 10 million. Is it possible. If yes kindly suggest some resources or references, where I can read about it.
At this time, the 10,000 topics and subscriptions limit cannot be increased. It is a dimension we'd like to scale up at some point, but for now, this is not a quota for which one can request an increase.
I'm designing the future notification system for an app, and wondering about how topic subscriptions work.
According to the documentation here the following note states:
Note: You can subscribe up to 1,000 devices in a single request. If
you provide an array with over 1,000 registration tokens, the request
will fail with a messaging/invalid-argument error.
Does that also mean that a topic can't have more than 1000 subscribers? Or would I be able to exceed that 1000 user limit if I register devices one by one?
From the docs:
Topic messaging supports unlimited topics and subscriptions for each app.
The note in this page, means the array can only have 1000 tokens in one request, if you add more than 1000 then you will get an error.