Inside WeWork's Tech Stack

Last week, our friends at Underdog featured a story about our Tech Stack written by one of our longest tenured Lead Software Developers, Ramin Bozorgzadeh.

Be sure to check out the last bit about how we focused on making the Rails based wework.com as performant as possible, through CDN caching, and a bit of nifty Javascript tinkering.

Some choice words:

“There are a number of ways to do this but the approach that we took involved loading our static homepage html from the CDN and then making a request for a very small piece of JavaScript as one of the first things in our page’s head…It first sets up the user’s session so that we can identify the user when running experiments and whatnot. It also retrieves some other data that we were originally putting into our Rails application layout…”

There’s a lot more to check out in the article over on Underdog where we talk about our custom systems built to manage our 25,000+ membership base.

Check back soon for a more detailed write up of our process.

Written by Matt Star
Software Engineer at WeWork. React. Redux. Front End.

Related Posts 10

How To Scale As A CTO - Why Course Correction Is Inefficient (Video)
Bridging digital and physical with a MakerBot Replicator 2
How I Aced my Technical Interview (by pretending to be a wizard)
Additional tips on improving scrolling performance of a UICollectionView
Why WeWork.com uses a static generator and why you should too
Rabbits, Bunnies and Threads
Adding columns with default values to really large tables in Postgres + Rails
Creating BEM Stylesheets for React Components
React Tutorial - Converting Reflux to Redux
Caching External APIs in Rails for a Ginormous Speed Boost