There are many interactive- many interacting parts. So building web apps at the scale that we operate at is quite demanding work, quite challenging. We have two mobile apps- TweetDeck, the recently launched analytics dashboard, the ads platform, Vine.īut we also have a bunch of smaller applications.Īnd we build web apps for specific audiences, partners, internal, like, defacing dashboards, all kinds of things.Īnd because we have a predominantly service-oriented architecture, sometimes we even have multiple apps that to a user look like one app.īut they're split up into multiple services. Some of the ones that you might think of off the top of your head are, the mobile apps. So at Twitter, we build and design a lot of web apps. So a brief history of how we got to the state where we need to build generic UI infrastructure, and the chances that we've had to learn from our prior experiences, and the problems that we've had with our existing applications. Once I moved to the US and I worked at Twitter, I joined the Cards team and was involved in creating the first new mcore service outside of .Īnd mcore is the name that we use internally for the Scala web server that Twitter created.īuild tools integrating a CSS preprocessor.Īnd I did a bit of related work on build tools and test infrastructure for some of our open source projects, too.Īnd that kind of has really helped inform the little that I know about infrastructure work and tooling. Once I joined Twitter, I worked at TweetDeck for a few months.Īnd while I was there, I ported their Python build scripts to Node using Grunt at the time. So before I joined Twitter, I kind of got into dotfiles, about automating your machine environment, having install scripts.Īnd that really sowed the seed of working with the file system, and taking some source files, and generating, like, output. So you might be thinking, I thought you do CSS? And I was thinking this, too.īut when I thought about it a little bit, it turns out that something I am quite interested in is infrastructure work.Īnd I've spent most of my time at Twitter working on it in some capacity. It's simply sharing what I've been working on with a colleague of mine, Rob Sayre, who's the tech lead of the web engineering at Twitter.Īnd I'm going to break it down into three sections- basically a brief history of the problems that we're facing and the way that we're thinking about dealing with them, the principles that we're using to guide the infrastructure work that we're doing, and then a brief overview of the system itself. It's not a success story or a sort of how to, or anything like that. So I hope that you'll find it interesting to hear about what we're working on. Give a big hungover welcome to Nicolas Gallagher.Īnd Twitter has, I assume, a series of uncommon challenges that, at the moment, necessity that we start building a UI infrastructure to make available to the rest of the company. Here to present a topic which is has been described on the Fronteers site as TBA, so something to look forward to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |