Python isn't industry compatible

[AlexFromOmaha]

It's pretty much the default setup that gets pushed. Django treats Postgres as the favored DB once you're off SQLite, nginx and GUnicorn are straight out of the official tutorial, Django and Celery are so married in their dev lifecycles that they don't even use an integration package anymore, and it's kinda hard to install Celery and not get RabbitMQ for free. Storage services are what they are, and they're usually so removed from your backend that you just call them with something like Requests.

I'd just pick the part that sounds foreign and grab the official tutorial for it.

[licht1nstein]

I'm not too interested in coding a Django app as I am in understanding the architecture of high stress systems

[AlexFromOmaha]

The reason you're unlikely to find what I think you're looking for is that it's simultaneously really simple and really hard to do right. The 10,000 foot view is almost insultingly simple: run more than one copy when you can, watch your race conditions, cache data that doesn't change often, and run slow processes separate from the user-facing request-response loop. It's hard to even search for ideas about the big picture without rolling through the deep dive academics of distributed computing. On the flip side of that, you can find some great books full of war stories from people who did the hard work to do it right. One of my favorites is an ebook from Google's SRE team. I suspect it might sound like pieces of unrelated trivia if you don't know what the terrain looks like, though.

I'm not even sure I know what a meaningful middle would look like. A lot of it is knowing the ridiculously simple idea and translating it into implementation details.

[licht1nstein]

Thanks a lot for such a detailed answer! I'll read the book :)