Messaging at Scale at Instagram

Rick Branson
As activity accelerated from just a few thousand activities per day to hundreds of millions, Instagram needed a reliable, scalable messaging infrastructure to distribute work and messages. In this talk, I'll jump from a crash course in t

[@kienphan6436]

great talk thank you!

[@kaoskitteh]

Great talk. Thanks!

[@OskarPaolini]

Enjoyed this very much, thank you!

[@Kideqx]

i love this stuff!

[@vvp8590]

No BS, to the point talk. Awesome.

[@hokcuan2390]

Watch it just now, still awesome!❤

[@jsilve1]

this is from 8 years ago. a lot has changed, in technology, business, etc. does insta still use Celery?

[@DJBenito304]

How does he get rid of the SHIM?

[@soufianosse333]

that's great :+1

[@drdzdd]

Great talk, but still don't get what this chained task thing is ..

[@rjs5613]

I think thats a simple recursive batch execution. The completion of the one batch triggers next with an offset.

[@gokukakarot6323]

think of it as pagination

[@DanVasquez0xFF]

15:37 this is not a good pattern you shouldn't call a task from another task that way. I would be better to create a workflow where check_url raises an error when spam is found and take_some_action is bound to the on_error task method of check_url. ex:
# in the caller
check_url.s(id, url).on_error(take_some_action.s(id, url)).delay()

[@ptitjo9475]

5:29

[@ptitjo9475]

9:30

[@jivanmainali1742]

Is redis user ID list unbounded and ever increasing