4 ms·
Instagram's backend is (mostly) a single, giant Django app. So it is possible to put together massive apps in it. I didn't have the time to delve into the archi
by 1letterunixname 3y ago
Instagram's backend is (mostly) a single, giant Django app. So it is possible to put together massive apps in it. I didn't have the time to delve into the architecture.
What I find lacking in most MVC backend frameworks lack is the componentization and composition of business rules in and across individual models. dry-rb and trailblazer were good efforts in this direction, but the reality is most backend apps in production stay mired in low-level implementation effort and duplicated code with whatever the MVC framework provides.
Also, the presenter pattern tends to require a bolting on in most frameworks.
- theptip 3y agoIt’s certainly possible, but is it a good idea? Would be interested in general sentiment from those working in that codebase. (Though FB uses Hack so I think there is a general tendency at Meta to scale whatever happens to have been used to build the first version, rather than decompose and rewrite some pieces.) IG’s Django must be pretty weird since the ORM will be driving Tao/Ent, rather than a normal SQL database? I wonder what the code looks like.
- bbrmaley 3y agothey ditched orm in favor of own implementation years ago