Earlier quoted context omitted.
It's a heavily modified internal fork of Django. Source: I work on our Python Language Foundation team.
Are you using the ORM/auth/admin features or is Django just a lightweight router? I can't imagine the ORM being too useful at Facebook's scale.
Backend of Meta Threads is built with Python 3.10
141–150 of 458 posts
Re: Backend of Meta Threads is built with Python 3.10
#142For the “Python isn’t fast enough for production backend” crowd from the same company that brought you the largest social network built on PHP + MySQL.
You mean the company that had to create their two PHP implementations and a translator to C++, to actually scale?
Facebook was already at a scale larger than 99.99999 percent of sites before they had HHVM
Re: Backend of Meta Threads is built with Python 3.10
#143For the “Python isn’t fast enough for production backend” crowd from the same company that brought you the largest social network built on PHP + MySQL.
Re: Backend of Meta Threads is built with Python 3.10
#144Earlier quoted context omitted.
Thanks for your comment. I'm really interested in this topic. How do you know the web server is Django? I searched but couldn't find this. Why would they use Django? I did some small projects in it but I assumed it wasn't very fast and wouldn't be suitable for a big app like this. I would like to know the pros and cons. Why didn't they build up something in C++ or Rust? Won't python limit the speed of responses despi…
Most of Facebook is built on PHP. I’m surprised they didn’t choose Laravel.
Re: Backend of Meta Threads is built with Python 3.10
#145Re: Backend of Meta Threads is built with Python 3.10
#146Ironic that a post about Threads backend is hosted on twitter.
If you want real irony here, it's this: powering an app called Threads with Python that's got a global interpreter lock which makes threading hard. Get it? Threads, threading...? OK, I'll see myself out.
Re: Backend of Meta Threads is built with Python 3.10
#147For the “Python isn’t fast enough for production backend” crowd from the same company that brought you the largest social network built on PHP + MySQL.
Re: Backend of Meta Threads is built with Python 3.10
#148Earlier quoted context omitted.
A fair point that it's stupid to implement a mostly plain text publishing site that doesn't support linking to any of the text published there. Edit: Someone kindly pointed out that you can see the content in the browser without an account from following a direct link. (You just can't have the app installed or it will open that and drop you on the login page.) This makes me a lot happier with the product!
You can link to it, what are you talking about? An example fetched from a verge article -> https://www.threads.net/t/CuVaOg1PgU4/
Re: Backend of Meta Threads is built with Python 3.10
#149For the “Python isn’t fast enough for production backend” crowd from the same company that brought you the largest social network built on PHP + MySQL.
It may not be because of Python, but Thread is definitely not ready for the current load. Few hours ago no one could access to Zuck's profile page, and he had to take it to private to hide the issue.
Re: Backend of Meta Threads is built with Python 3.10
#150Earlier quoted context omitted.
How is Django now? I’m a long time python dev (data eng space) but new-ish to web dev. I started a Flask project 2 years ago and found it to be pretty full of footguns, mixed messaging on best practices for scalable apps, and the ecosystem feels overbloated with vapor ware extensions. Is this just a Flask problem, or does Django have the same issues?
I use django professionally and for personal projects. I started with Flask and then did FastAPI for a while, but I like django the most since it's the most mature. The ORM and django admin are killer features out of the box that the other frameworks don't have. I will say though that FastAPI is really nice, especially if you need async support. However, I have found that using django ninja [1] adds a lot of nice to…