sending more than 10,000 sms

I would definitely suggest using the queue as the response time would be immense i expect. Maybe grouping them in batches? I'm not the best person but i think queues are the way forward

I am pretty sure they have some api the handle bulk sending... so start by checking theire api

@Goldenstat do you mean using chunk , each job will send 100 sms ??

Contacts::chunk(100, function ($contacts ) {
    $this->dispatch(new SendSMS($contacts )); 
});

@boynet no they dont , they are sending 1 sms per sec, each request will send just 1 sms

@Sulieman Sort of i meant more as

$contact = Contacts::all();
$chunk = 0;
$i = 0;
$group = [];
foreach ($contacts as $contact) {
    $i++;
        $group[$chunk][] = $contact;
    if($i == 10)
    {
        $chunk++;
    }
}

Then dispatch the array?

@Sulieman Use the queue. You do not want to be trying to send 10,000 SMS message via a HTTP API in a single page load. If one fails and kills the loop, or the page load times out (or a hundred other scenarios where things can go wrong), how do you know which one it was and where to pick up again?

Instead, use the queue component. It’s exactly what it’s built for. Add a job per SMS, and have a queue worker run them. The queue worker will process each SMS one at a time. If you need SMS messages to be sent quicker than that, then that’s where you would scale and have more than one worker working on your queue. The theory is: twice as many queue workers would process the queue in half the time.

Some example code:

foreach ($users as $user) {
    $this->dispatch(SendSmsToUser($user, $message));
}

Your SendSmsToUser job class will need to know how to fetch an SMS number for a user. And you’ll also need to specify the $message body.

@martinbean , yes , and then when the worker make a job i can insert a row in the database and save the status for that sms, this way i will know exactly wich sms sent and wich not

but my question if the loob to inset 10000 job will work fine on the server ?

foreach ($users as $user) {
    $this->dispatch(SendSmsToUser($user, $message));
}

i can insert a row in the database and save the status for that sms

@Sulieman There’s no harm in doing that, but you will know if an SMS is sent or not by whether it has been removed from the queue or not. Queues will usually attempt to process a job a set number of times and if the job fails, will be placed in a “failed” table in your database for manually investigation. Jobs where the SMS has been successfully sent will just be removed from the queue once processed.

Do note that Twilio has some sending limits, so you may want to throttle the speed at which you send the messages: https://www.twilio.com/help/faq/twilio-basics/what-are-the-limits-on-outbound-calls-and-sms-messages-per-second

Do I understand correctly 1 sms per second ? That means if you would like to send 10 000 sms it will take 10 000 seconds ? Or maybe this is different kind of calculating overall time ?

@monsterdream yes it 1 sms per second . If more messages per second are sent, Twilio queues them up and sends them out at a rate of 1 per second.

@Sulieman What a crap. I've done for my client sms system where his clients send for example 4000 sms and it takes something about 1 min... For a second I thought maybe those services you mentioned above are worth my interest but... No.

@monsterdream do you know another services that allow sending more than 1 sms per sec ?

@Sulieman You can try FortyTwo. I'm not specialist, He just gave me login data for that service.

https://www.fortytwo.com/

It looks like it is a Canada / US global issue, and not a service specific issue :

https://help.nexmo.com/hc/en-us/articles/204024183-Canada-direct-route-

1 SMS / second

Question : did anybody reached this with Queue and throttle ? where do I set the rate limit ?

Thanks

Hello, how were you able to implement the sms with jobs. need some help on this. doing similer.