Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Presentation
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
Scaling the Social Graph: Infrastructure at Facebook
- Sections
- Architecture & Design
- Topics
- MySQL ,
- QCon San Francisco 2010 ,
- Stories & Case Studies ,
- Relational Databases ,
- QCon ,
- Performance & Scalability ,
- Architecture ,
- Agile ,
- Database ,
- Conferences ,
- Facebook ,
- Social Networking
-
- The next QCon is in New York June 18-22, Join us!
How would you like to view the presentation?
In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
Jason Sobel presents the evolution of Facebook’s infrastructure over time, from the original LAMP stack to the present multi-datacenter configuration, the challenges faced and plans for the future.
Bio
Jason Sobel is an engineering manager on the Infrastructure team at Facebook where he focuses on keeping the site fast and scalable. He helped develop Facebook's multiple datacenter strategy and also worked on Haystack, Facebook's custom built photo storage infrastructure. Before joining Facebook Jason was a member of the WAFL team at NetApp where he worked on file system performance.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Jason Sobel presents the evolution of Facebook’s infrastructure over time, from the original LAMP stack to the present multi-datacenter configuration, the challenges faced and plans for the future.
Bio
Jason Sobel is an engineering manager on the Infrastructure team at Facebook where he focuses on keeping the site fast and scalable. He helped develop Facebook's multiple datacenter strategy and also worked on Haystack, Facebook's custom built photo storage infrastructure. Before joining Facebook Jason was a member of the WAFL team at NetApp where he worked on file system performance.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
RelatedVendorContent
Introducing SQLFire: a memory-optimized, high performance SQL database
Related Sponsor
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
- See more Agile content at: http://www.infoq.com/agile
- See more QCon content at: http://www.infoq.com/qcon
- Other recent content items in this topic
Scribe
by
Robert Sullivan
Posted
Video is broken after 20 or so add minutes.
by
Janarthanan Poornavel
Posted
Presentation Slides
by
Vinh Vo
Posted
-
Great presentation!
I'm sure there are those who will say "Why reinvent the wheel, when perfectly good technologies exist", in regards to Scribe (MQ Series etc) and Thrift (CORBA (faster), REST and HipHop (phc).
However, don't we all do this? This is the classic build or buy or use OSS scenario. Sometimes you simply don't have the option, and you are challenged write, as a colleague of mine did, amazing pieces of code, such as a queueing system using SQL Server stored procedures - since we didn't have access to a commercial or open source queue application like MQ Series at the time. I remember saying to the coder that I didn't know you could do stuff (spawning off threads, etc) like that with MS SQL Server, and he replied he didn't either!
When confronted with a complex technology like CORBA, isn't that why everybody went with SOAP? I.e. the developer may run into some issue with technology X, and thus conclude it would simply be faster if they built it themselves, to their own requirements, rather than get bogged down in poor documentation and overly complex integration, with little perceived benefit. I.e. if all I need is an IoC, so that my code is "loosely coupled", do I really need the heavy-weight, xml conf burdened complexity of Spring, or simply build my own version, with the newer technology available, as Google did with Guice, using annotations?
Sure sometimes technologies start out simpler - Java as a simpler C++, SOAP as a simpler CORBA. I believe the "S" standed for "simple", at least at one point.
And I am sure there are benefits of Thrift, and Scribe, perhaps easier install, simpler than CORBA, (although this is less true with today's excellent CORBA implementations (omniORB), that are highly-efficient and easy to use.)
Now, the only downside to this is that now you have another non-standard protocol, so that you get crazy stuff like not being able to cut and paste and share info between Linux systems if they are using different UI frameworks, i.e. KDE uses kparts, a sort of COM-like framework, and GNOME uses something else, probably custom also, they did have a CORBA implementation, but didn't take off.
Now, if you are a heavyweight like Microsoft, or Google, or Facebook, who cares, because you are the 800lb gorilla and everybody else has to follow your model, but at least with Facebook it seems they are (for now) contributing back to the open source world they built their empire on - so that's cool.
Thanks again for the post! -
Looks like the video is broken. I even tried scrolling past the problematic point, it did nt help.
-
Could you please share the slides?
3 comments
Watch Thread Reply