This seems like a fine time to look back on the rather decent API platform our team built at Twitter.

RT @THISWILLWORK: I am going to miss this place. We built something special here, and I do not expect to see its like ever again. I have wo….

Fired a little less than 8 years in the tweet mines. I loved working here.

Couldn't agree more strongly.

RT @sachee: you did not just layoff almost all of infra and then make some sassy remark about how we do batching . like did you bother to e….

RT @LouPas: @elonmusk Elon, Great chat yesterday, As you heard overwhelmingly from senior advertisers on the call, the issue concerning us….

RT @mikecvet: I think its fair to say that new management is entering the “find out” phase.

RT @CharlieCroom: This dude is laying off thousands right now, has said nothing all week, can't be bothered to sign the letter, and doesn't….

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.

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 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.

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.

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.

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!?.

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.

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.

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.

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.

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.