DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations

How Facebook Does Deployment

Mitch Pronschinske user avatar by
Mitch Pronschinske
·
Apr. 06, 12 · Interview
Like (1)
Save
Tweet
Share
34.06K Views

Join the DZone community and get the full member experience.

Join For Free
Some interesting insider info was released this week about the Facebook deployment process.  I've compiled a TL;DR version here in case you don't want to read the whole piece, but I recommend you do.  The information comes straight from Chuck Rossi, the head of Facebook's release engineering team, who was interviewed by Ars Technica's Ryan Paul:

An important aspect of Facebook's development culture is the idea that developers are fully responsible for how their code behaves in production. This philosophy mirrors the "DevOps" movement, which encourages lowering the wall between software development and IT operations.

If any of the code in a Facebook update causes problems in production, the developer who wrote it is on the hook for making sure that the issue gets resolved as quickly as possible.

--Ryan Paul, Ars Technica "Exclusive: a behind-the-scenes look at Facebook release engineering"

I think we've got more evidence here that "DevOps" is just a name for what many super-successful companies have already been doing.  On to the TL;DR!

For deployment Facebook uses


  • Uses custom BitTorrent P2P system
  • Site updates take 15-30 minutes
  • JS, CSS, and Graphics are hosted on distributed CDNs

Deployment steps


  1. Update goes to an "a2"  tier which rolls update out to a small, random collection of users.
  2. Check-in procedure on company IRC where all developers who submitted code for the update have confirm that they are ready to respond if there is a problem when the update goes out.
  3. Head of release engineering issues command in terminal to begin deployment
  4. Watch web-based monitoring dashboards as the update rolls out.

A small amount of servers will fail during most deployments, but it usually doesn't cause any issues.  That's because any of Facebook's servers can handle any sort of page request, so they don't have to worry about serialization and migration of user session states.  The servers can keep handling incoming page requests during their software updates.  No-downtime, as we all know.

Frequency of deployments:


  • One minor update on most business days
  • One major update on a weekly basis, usually Tuesdays

"Release early and often."  The mantra rings true at Google, Facebook, and many other companies that we look up to as the best in the business.

Make sure you check out the whole article for the full story on Facebook's release engineering.
facebook

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • DevOps vs Agile: Which Approach Will Win the Battle for Efficiency?
  • Is DevOps Dead?
  • Comparing Map.of() and New HashMap() in Java
  • 10 Best Ways to Level Up as a Developer

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: