James Bellenger Profile picture
Nov 3 12 tweets 2 min read
This seems like a fine time to look back on the rather decent API platform our team built at Twitter.
THE YEAR IS 2017. Building new features for the bird app means exposing new data over Twitter’s APIs. This involves coordinating changes across many services and many teams, because microservices.
Flash forward to 2022. Over 5 years, we’ve migrated almost every api used by the Twitter app into a unified graphql interface. Getting api changes into production used to be measured in weeks, now it's measured in hours.
For the last 2 years, EVERY SINGLE new Twitter feature was delivered on this api platform. Twitter blue, spaces, tweet edit, birdwatch, and many many many others.
This api platform serves your home timeline, every tweet embedded in your favorite nytimes article, and the entirety of the 3rd-party developer api which uses our graphql system to fulfill every part of every api request.
Just in this calendar year, there have been over 1000 changes to this graphql api by over 300 developers at Twitter. The api serves 1.5 BILLION graphql fields per second across 3000 different data types. The system is vast, developerable, and efficient.
Getting to this point didn’t happen overnight. It was slow! It was hard! It wasn’t always clear that it would work. What if it took too long!?
We got here with deep & long-term commitment of engineering leadership. Managers grew a team around an early prototype, directors prioritized api migrations, and partner teams front-loaded integrations with the platform without knowing if/when their work would pay off.
This platform has been a critical but invisible part of powering nimble product development at twitter, reaching literally millions of users every hour of every day.
The pace of product changes that are (and will be) coming to Twitter would literally not be possible without the long-term investments we’ve made in building this api platform.
I’m exceptionally proud of what our team has built over the last 5 years. It is hardcore engineering at scale, solving difficult problems, built humanely.
The team that built this platform are the kindest and most talented humans that I’ve had the privilege of working with.

Thank you.

#OneTeam

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with James Bellenger

James Bellenger Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(