zlacker

[parent] [thread] 4 comments
1. maccar+(OP)[view] [source] 2023-08-30 21:31:19
I think Airbnb is the worst offender by far though. Instagram, Facebook and Twitter (just using your examples) operate very dynamic applications at a global scale. AirBnB is a crud app with almost no dynamic content other than the booking system. According to the first site I saw online, they process 6 bookings per second, which I could handle on literally anything with an internet connection. Of all of them, its the one I understand the least.
replies(1): >>steve_+V6
2. steve_+V6[view] [source] 2023-08-30 22:11:57
>>maccar+(OP)
I thought this sounded way too low but the most generous figure I can find is 12 per second in 2022. What the hell? I thought it would be more. Should I have thought that? I guess not.
replies(1): >>sa46+Jj
◧◩
3. sa46+Jj[view] [source] [discussion] 2023-08-30 23:46:07
>>steve_+V6
6 bookings per second at $200 per booking is $103M processed per day.

Each booking likely represents dozens to hundreds of requests. Then, for every visit resulting in a booking there’s probably hundreds of non-booking visits.

replies(2): >>maccar+9l1 >>lopken+bT1
◧◩◪
4. maccar+9l1[view] [source] [discussion] 2023-08-31 09:27:30
>>sa46+Jj
> 6 bookings per second at $200 per booking is $103M processed per day.

I don't doubt that they don't prcess a lot of money - that's besides the point.

They're a cookie cutter CRUD app (that happens to process a lot of money) that takes _hundreds_ of requests and 12 seconds to load on a 32 core workstation with a gigabit fibre internet connection. They have no business writing a blog on performance engineering.

◧◩◪
5. lopken+bT1[view] [source] [discussion] 2023-08-31 13:14:43
>>sa46+Jj
If your CRUD app's booking endpoint internally fans out to 100s of requests, you're doing something extremely wrong and/or you've dug yourself into microservice hell.
[go to top]