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:
It Is Possible to Do Object-Oriented Programming in Java
- Sections
- Architecture & Design,
- Development
- Topics
- QCon London 2011 ,
- Java ,
- OOP ,
- Languages ,
- QCon ,
- Methodologies ,
- Conferences ,
- Programming
-
- 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
Kevlin Henney takes a philosophical approach to encapsulation, polymorphism and inheritance, and explains what it means to write Java programs according to his view on OOP.
Bio
Kevlin is an independent consultant and trainer based in the UK. He has been a columnist for various magazines and web sites, including Better Software, The Register, Application Development Advisor, Java Report and the C/C++ Users Journal, co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, and editor of the 97 Things Every Programmer Should Know.
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.
Kevlin Henney takes a philosophical approach to encapsulation, polymorphism and inheritance, and explains what it means to write Java programs according to his view on OOP.
Bio
Kevlin is an independent consultant and trainer based in the UK. He has been a columnist for various magazines and web sites, including Better Software, The Register, Application Development Advisor, Java Report and the C/C++ Users Journal, co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, and editor of the 97 Things Every Programmer Should Know.
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
The WebSphere Liberty Profile for Developers: An Introduction
Related Sponsor
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
- See more Java content at: http://www.infoq.com/java
- See more QCon content at: http://www.infoq.com/qcon
- Other recent content items in this topic
Wonderful presentation
by
Adam Nemeth
Posted
Impl? No. Well... how about "not for long"?
by
J. B. Rainsberger
Posted
Re: Impl? No. Well... how about
by
bruce b
Posted
Type of a presentation where...
by
Yuriy Zubarev
Posted
-
I'm always surprised by Kevlin's broad literacy on programming subjects, and the ability to go from very-very high level concepts to actual code level consequences.
This presentation shows that the SOLID principles of encapsulation, substitution and interface-dependency have deep inter-relatedness. It shows different aspects of these in virtually unrelated technologies, like C, C++, Java, COM and Javascript. It seems it recommends to shift the ADT taxonomy to interface inheritance in order to reach pure object-orientedness.
What I miss is the expansion of the object/class concept from a perceptional view. I think it's a very interesting question of how the notion of classes sneaked in to the object-oriented paradigm, but perhaps this presentation simply wasn't about this. -
I prefer to interpret Kevlin's comment "Impl? No." a bit differently: if I don't yet know what makes a particular implementation of an interface different, then I will name the class XImpl; however this suffix "Impl" (like "Factory", "Singleton", "Manager", "Policy"...) signals a purely structural name which, while useful, restricts my understanding of the design. After some time, as I learn what makes this particular implementation significant within the context of the system, I rename XImpl to SignificantPropertyX, where "SignificantProperty" is an aspect of the implementation that matters in the current design. This corresponds quite nicely with Kevlin's example here. I don't know that "RandomAccessRecentlyUsedList" means more than "RecentlyUsedListImpl" when we don't yet know whether random access matters in the design.
I have summarised an approach to improving names here: link.jbrains.ca/ovMMvz -
... you learn couple of important things, and realize that you don't fully comprehend dozen of even more important ones.
Commendable job Kevlin! -
If the interface has one implementation, then you're going to be stuck with some generic naming convention: Impl, Default, Standard are all ones that I've seen. Besides if you follow his advice and the concrete implementation is only referenced with the new operator, then what's the big deal?
4 comments
Watch Thread Reply