The first story is about how we deal with changing our API and just generally how we evolve the Stripe API. One of the things that we consider to be important about the Stripe API is that once you have integrated with it, you don’t have to change your code. It should work sort of in perpetuity because most people don’t care about it. We care about evolving our API. But if you have already written code and it works, you don’t care about changing that and so we don’t want to require you to change your code just so that we can do things that we think are interesting and different and innovative. So I am going to talk about some of the technical strategies that we use to actually implement that and how we support that on our backend and make it possible for us to change the API without affecting system users.

The last story has to do with an infrastructure migration. This is something that we did last November. We migrated our entire infrastructure both from EC2 Classic, AWS's legacy networking environment, into VPC and also across regions from one region to another and so, we did this and an entire data center migration. We did it in the course of about 4 or 6 hours with no user visible downtime or any real latency impact. The important part of that story is that the way that we were able to do this effectively and without impacting our users was that we looked for points of super high leverage. We tried to find as many shared pieces of infrastructure as we could and solved problems at those layers to try and minimize the impact on the rest of the organization and sort of the amount of blockers that we had to do work through in order to make the migration move forward.