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:
Infinitely Extensible
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
Alex Papadimoulis discusses avoiding over-engineering a program, presenting extensibility types used, extensibility design patterns, when to use them, and what happens when they are incorrectly used.
Bio
Alex Papadimoulis is the founder and editor of The Daily WTF, a leading how-not-to guide for developing software. Residing in Berea, Ohio, he is a software engineer at Inedo and uses his 10+ years of IT experience to help software development organizations utilize best practices in their products though BuildMaster, a next-generation ALM suite.
About the conference
Code PaLOUsa is a conference designed to cover all aspects of software development regardless of technology stack. It has sessions revolving around Microsoft, Java, and other development platforms; along with session on higher levels that are platform agnostic. The conference schedule will feature presentations from well-known professionals in the software development community
Alex Papadimoulis discusses avoiding over-engineering a program, presenting extensibility types used, extensibility design patterns, when to use them, and what happens when they are incorrectly used.
Bio
Alex Papadimoulis is the founder and editor of The Daily WTF, a leading how-not-to guide for developing software. Residing in Berea, Ohio, he is a software engineer at Inedo and uses his 10+ years of IT experience to help software development organizations utilize best practices in their products though BuildMaster, a next-generation ALM suite.
About the conference
Code PaLOUsa is a conference designed to cover all aspects of software development regardless of technology stack. It has sessions revolving around Microsoft, Java, and other development platforms; along with session on higher levels that are platform agnostic. The conference schedule will feature presentations from well-known professionals in the software development community
RelatedVendorContent
Requirements, quality and test management e-Kit
Architectures You've Always Wondered About @QCon New York
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
Combining Inspections, Static Analysis, Testing to Achieve >95% Defect Removal Efficiency
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!
- This article is part of a featured topic series on Agile
- See more Agile content at: http://www.infoq.com/agile
- Other recent content items in this topic
Exactly these codes will end up at the Daily WTF
by
Adam Nemeth
Posted
-
The main property of f.ing failures is that everyone believes they do the best job possible. They don't want too much overhead of course, whatever that means for them - wether be dumb work or cleverness - yet somehow projects still end up on that website.
I've seen applications on a daily basis where they followed Alex' advice, like, they actually forked an application instead of providing clever extensibility, ending up with managing two full applications for more than 10 years, where one even had to stay in an unsupported platform. I see code without any design patterns or config files.
The only reason those codes didn't end up at Daily WTF is usually NDA. A full team of outsourcing company can laugh at you just before committing such errors themselves.
So, remember: that f.ing dumbass who did that crap and can't code, in the eyes of your project's next maintainer (or the first one who doesn't know you) is you!
1 comment
Watch Thread Reply