> It can handle more than 500,000 orders per month
How many seconds in a month? 60 * 60 * 24 * 28 = 2,419,200.
So basically, its performance is at least 0.2 requests a second...
How many seconds in a month? 60 * 60 * 24 * 28 = 2,419,200.
So basically, its performance is at least 0.2 requests a second...
(Not that I want to defend Laravel's speed, it's not really anything to brag about, and the typical "cache everyhing everywhere all the time" aswer is not that useful.)
Not to mention that as long as you have a direct sync query to a database - your code will have to wait, lol.
OTOH it makes a point that it solves a real problem. A business processing 500k orders a month is not trivial.
It all sits in a single 5 year old machine with 8 cores and 16GB RAM. Their bottleneck is actually MySQL but they have room to spare so no need for upgrades right now.