Python Not Recommended
summary
Braintree uses Tornado-based proxies for high-concurrency incoming and outgoing request handling but hits concrete failures: outdated Tornado, Python 2 concurrency limits, logging stalls, missing SNI and maintenance overhead that forces callback-heavy code and brittle, over‑coupled business logic. Replacements include Nginx + HAProxy + PgBouncer for incoming traffic and a planned JVM/Kafka rewrite for outgoing proxies (Node attempt fails due to leaks). Python survives for data science, infrastructure automation, and a single py2/py3 client library.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:23The Radar
- 0:42Python Not Recommended
- 1:20Ruby Ecosystem
- 1:36Python
- 3:23When to use Ruby
- 4:10When to use JVM
- 4:30When to write a smart proxy
- 4:57Uptime requirements
- 6:36Tornado
- 6:54Python in 2013
- 7:11Python failed
- 8:00Python maintenance overhead
- 8:49Smart proxies
- 9:31Not smart enough
- 10:07Incoming requests proxy
- 10:46Outgoing proxy
- 11:32Enclosure
- 12:12Smart Proxy
- 12:24Internal Advocates
- 12:41Python Outside of Work
- 15:59Python Community
- 16:27Python Hiring
- 16:42Python Talks
- 18:35Questions
related talks
42mBuilding a hosting platform with Python
42mBuilding a hosting platform with Python
36mA Python Takeover
30mDesign and implement a scalable and high performance tcp server with tornado
01h 02mUsing Python to Power Serverless Applications
30mPython for developing an automated trading platform
36mA Python Takeover
26mPython as a Universal Backend