How to properly organize push notifications?

Question

SMS

There is a task: designing a service for sending messages by subscribing to a distribution channel.
The bottom line is to deliver messages to more than 10k clients with frequent intervals.
There is a certain entry point - a public API to which the text of the message and the distribution channel will come.
All logic for message delivery (worker / worker) is planned to be moved to Amazon Lambda.
I'm thinking about using a message queue. But there are doubts which of the options will be correct.
1. When receiving the mailing text on the API server, generate 10k messages in the queue.
I highly doubt this option.
2. Throw the message into the database with a mark for further processing and a separate worker to go through these messages and generate a queue of 10k recipients.
A very important criterion is the scalability of this miracle.
I will be glad to any information, articles, reports, books...

Answer 1

There are no PUSH notifications in GSM (except for WAP PUSH), but I don't think you need them.
As for SMS/USSD messages, there are several options.
1. Form a queue from SMS (1 number - 1 text)
2. Form a list of numbers + a single text
and throw it towards your gateway (for example, based on kannel) or towards api provider (for example, now
sms ).
If we are talking about push notifications ( ios / android ), then without an installed application you can’t work with them.
If you have an appliquha on your pipe, smoke Google Fire Base.