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.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Taming HTML5 and JS: High Performance Mobile, WebKit, FireFox Dev Tools @QCon New York
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
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!
There's nothing new here, just some old code refactoring advice...I mean, "..breaking a long line of code into separate lines.." can hardly be considered ground breaking advice that most people dont already know about..He could have probably finished his talk in 5 minutes without going on and on endlessly...
C'mon infoQ, please don't become another "serverside.com" by posting crappy stuff…We expect better quality from you...
I've liked this talk. The point is that developers know how to make code more readable but don't understand how important it is. Even if given advices are all well known the problem of crappy code is still problem of today and it's interesting to know what other people think about it.
Nice talk.
Even though I read refactoring book. Even though this nothing new . I think this is useful for new generation of developers who just started programming.
I like this and I can show this to my junior developers or even seniors who still doing same mistakes because they did not read refactoring book.
regards
Dear Anonymous Avid Fan,
As you pointed out, good practices were, are and will be the same as long as the values that we hold are still the same. Unfortunately nowadays learning a new language (usually per year) has become more valuable than writing good code. One of the rant's is that as obvious as the "breaking one line of code" is, you will see a lot of code from *any* developer breaking this rule. How come? And that happens even more when we switch to another language. If I could sum up, learn the language, and above all, learn to control yourself, avoiding idiomisms as they can become the next developers hell.
Regards
Exactly Oleg. I am ashamed of every code that I have written until yesterday. And will feel the same about it tomorrow. As long as I keep worrying about the quality - and not the purity or beauty - of my code/design/architecture, I might provide the next developer's paradise when I leave (or die).
I realize I may have come across as quite harsh in my comments, my sincere apologies for my poor choice of words earlier.
Actually, my comment was written in the heat of the moment..I guess, after reading the title and summary of the talk, I was expecting something else, and that caused the frustration at the end...So, again, my sincere apologies for the way i said it earlier...
The talk does not look very revolutionary, but that was not the point. The things mentioned are all among the most painful ones I must deal with on a daily basis. This and similar talks will have its place until it starts getting better even it the most "conservative" environments.
Just adding some humor to the presentation would make a big difference in its impact...
Although it's nothing new, I liked the new way he approached the subject.
And I added this (adapted) phrase to my white board: "Don't hide complexity. Make it easier to understand".
Something wrong with the sides download link
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.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
10 comments
Watch Thread Reply