InfoQ

Presentation

Recorded at:
Recorded at

Architectures of extraordinarily large, self-sustaining systems

Posted by Richard P. Gabriel on Aug 29, 2008 04:18 AM

Community
Architecture
Topics
Enterprise Architecture ,
Design ,
Modeling ,
Fault Tolerance
Tags
QCon ,
Scalability ,
QCon San Francisco 2007
Summary
Picture a system so large it cannot be comprehended. Can such a system be "designed" in any conventional sense? Will machines help design it? Will it help design itself? How will it keep running? Will it be alive? The foundations of computing are about to change. In this talk, Richard P. Gabriel explores why and how.

Bio
Richard P. Gabriel has a PhD in CS from Stanford, and an MFA in Poetry from Warren Wilson College. He's been a researcher at Stanford, President and CTO at Lucid, Distinguished Engineer at Sun and is now a Distinguished Engineer at IBM Research where he looks into architecture, design, and implementation of extraordinarily large, self-sustaining systems and techniques for building them.

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.

4 comments

Reply

Fascinating by Faisal Waris Posted Aug 31, 2008 8:57 AM
Reference by Mikhail Franco Posted Sep 1, 2008 1:47 AM
Hmm... by John Leach Posted Sep 19, 2008 4:34 PM
Re: Hmm... by John Leach Posted Sep 19, 2008 4:36 PM
  1. Back to top

    Fascinating

    Aug 31, 2008 8:57 AM by Faisal Waris

    I remember from my AI course last year the idea of "Cultural Algorithms" (Prof. Robert Reynolds of Wayne State) that seems to suggest that digital evolution can be more or less a continuous process - a part of the system itself.

  2. Back to top

    Reference

    Sep 1, 2008 1:47 AM by Mikhail Franco

  3. Back to top

    Hmm...

    Sep 19, 2008 4:34 PM by John Leach

    Couldn't we say that the internet internet would be a ULS?

  4. Back to top

    Re: Hmm...

    Sep 19, 2008 4:36 PM by John Leach

    just one internet... :)

Educational Content

JRuby: The Pain of Bringing an Off-Platform Dynamic Language to the JVM

Charles Nutter discusses bringing JRuby to the JVM, why Ruby is hard to implement, JIT compilation, precompilation, core Ruby implementation, Java library access, library challenges and future plans.

Performance Anti-Patterns in Database-Driven Applications

Alois Reitbauer specifies several architectural anti-patterns that one should stay away from and which can downgrade an application’s performance.

Making TDD Stick: Problems and Solutions for Adopters

Teams in large organizations still struggle to adopt TDD. In this article Mark Levison shares problems he uncovered when he surveyed teams, and his own strategy to introduce TDD into an organization.

Testing is Overrated

In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?

VM Optimizations for Language Designers

John Pampuch discusses the HotSpot compiler, the history of Java performance, HotSpot development philosophies and challenges, optimization, JVM library improvements, and tips for better performance.

Keith Braithwaite, an Agile Skeptic

In this interview, Keith Braithwaite, an Agile developer, consultant and trainer, says that we should show a good deal of skepticism towards today’s Agile practice.

Workflow Orchestration Using Spring AOP and AspectJ

This article demonstrates how to build and orchestrate highly configurable and extensible yet light-weight embedded process flow using AOP techniques with Spring AOP and Aspect J.

Embrace Uncertainty

Jeff Patton explains why one needs to embrace uncertainty in order to succeed with his/her Agile project and how to avoid some of the common mistakes leading to project failure.