Stripe had to rewrite key services from Ruby to Java for performance
“Or not early on in Stripe's history, early on in kind of our our collective personal history.”
one of our cofounders, interned Stripe early on. Or not early on in Stripe's history, early on in kind of our our collective personal history. Uh-huh. And, he remembers there being documents upon documents about a potential Java migration.
Yeah. So we, that partly happened. As in we have rewritten a bunch of key services on Java. And so some services for which, I don't know, throughput throughput in particular, is, is really important. And Mhmm. If you torture Ruby enough and, you know, maybe rewrite,
About this clip
Patrick Collison discusses Stripe's technical evolution, revealing how the company had extensive internal documentation about migrating from Ruby to Java. He explains that they partially executed this migration, rewriting critical services in Java when throughput performance became essential, acknowledging Ruby's limitations under heavy load.
Why this clip
Provides insider perspective on a major technical decision at one of the most successful fintech companies, showing how even well-established startups must evolve their tech stack.
More from this guest
Patrick Collison
1 appearance · 6 clips
What they said next
Stripe's 12-year API evolution from v1 to their major 2022 redesign
28:01 - 41s · tactical advice
More from this episode
Similar clips from other shows
From the blog
Want clips like this for your podcast?
We find your top 5-8 clips, write the hooks, and deliver ready-to-post content. First 2 episodes are free.
Get 2 Episodes Clipped Free