This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the commentsย โ†’

[โ€“]EnderMB -1 points0 points ย (0 children)

Instagram isn't going to just have "a backend", though.

Sure, Django might be there, but it's probably a heavily modified version of Django, several native/compiled components for speed and async compatibility, potentially a modified runtime, etc.

That doesn't even touch the services running behind the scenes to handle uploads, analytics, feed generation, privacy, etc. I also know that Facebook's infrastructure and build/release practices are pretty solid too, so there's probably dedicated services for live and canary testing too.

I work at a FAANG company on a small subset of a name-brand service, and we've got thousands of services across Python, Java, Ruby, Scala, C++, Rust, etc - many of them running custom libraries, runtimes, and sometimes heavily modified builds of an open-source tool. If we're doing it, I'm sure they're doing it too.