From Python to Java

As software engineers we do trade-offs every day. We often need to pick between things like space vs time or budget vs scope. Or sometimes the amount of creative waste we can afford to have. And when we make the decision we need to be in full comprehension of both the upside and downside of a particular choice. In this talk we will discuss why our organization decided to move from Python to Java. We will go over each tradeoff we decided to do and the motivation behind it.

Transcript

1. From Python to Java @stoitsev
3. June 1st, 2010 - Uber is founded Dec 24th, 2015 - 1bn trips June 18th, 2016 - 2bn trips
4. every time you think you are here
5. turns out you are still here
6. Тradeoffs
7. Microservices
8. Users Products Trips Cities Payments Receipts
9. Best tool for the job
10. Velocity
11. Training / Best practices / Documentation / Experts Project template / Bootstrapping Configuration Debuggers Profilers Building, Packaging, Deploying
12. Solving the same problems multiple times
13. TChannel clients Auth Schemaless client Logging, configuration, monitoring...
14. Development Cost
15. Operational Cost
16. Code Sharing
18. Broad Applicability
19. High Performance
20. Static Typing
22. Organizational Scale
23. Runtime Performance
24. Lack of concurrency
26. Community
27. Powerful toolchains
28. Ecosystem of high-quality libraries
29. http://benchmarksgame.alioth.debian.org/u64q/python.html
32. eng.uber.com/euclid
35. uReplicator https://github.com/uber/uReplicator
37. Proven
38. Momentum
39. Performance
40. Geofence
42. Thanks! eng.uber.com uber.github.io