Enterprise Integration Patterns
Gregor's Ramblings
HOME PATTERNS RAMBLINGS ARTICLES TALKS DOWNLOAD BOOKS CONTACT

Web 2.0 Patterns

Aug 24, 2006

Gregor HohpeHi, I am Gregor Hohpe, co-author of the book Enterprise Integration Patterns. I like to work on and write about asynchronous messaging systems, service-oriented architectures, and all sorts of enterprise computing and architecture topics. I am also an Enterprise Strategist at AWS.
TOPICS
ALL RAMBLINGS  Architecture (12)  Cloud (10)  Conversations (8)  Design (26)  Events (27)  Gregor (4)  Integration (19)  Messaging (12)  Modeling (5)  Patterns (8)  Visualization (3)  WebServices (5)  Writing (12) 
POPULAR RAMBLINGS
RECENT

My blog posts related to IT strategy, enterprise architecture, digital transformation, and cloud have moved to a new home: ArchitectElevator.com.

I confess. I am a groupie. When Tim O'Reilly invited me to be part of on a workshop on Web 2.0 patterns I was quite excited. First, because I was going to meet the exalted one in person. Second, because I would have a chance to learn a lot about Web 2.0 as I am pretty much starting from zero (working for Google does not automatically mean working on super-secret next generation massive computing projects). Lucky for me, the other participants are quite entrenched in the Web 2.0 phenomeon. Amongst others we had Bill Scott from Yahoo!, Jennifer Tidwell, Cal Henderson from Flickr, John Musser who runs ProgrammableWeb, Martin Fowler, and Sandy from Meebo.

The goal of the workshop was to build on Tim's paper What is Web 2.0. The paper cites a few examples that demonstrate the shift in thinking from Web 1.0 to Web 2.0:

These examples alone show a clear shift from publishing towards sharing and participation, a richer user interaction, and a stronger focus on sharing data. Our day-long workshop aimed to distill values, principles, and patterns of Web 2.0 (Martin recommended that we "borrow" this structure from Kent Beck's XP book).

Attributes of Web 2.0

We started by brainstorming what Web 2.0 means to us. As expected we ended up with a wide spectrum of ideas, which we then sorted into categories. One of the most interesting parts for me were the many examples that I had not yet heard about, such as:

Values

We tried to compile a set of values, along the lines of the Agile Manifesto. The key with the agile values is that is used a "X over Y" format where Y by itself is a fairly reasonable goal. For example, the value is not "Working Software over Broken Software" (duh!) but "Working Software over Comprehensive Documentation". Here are some of our candidates:

Other Cool Stuff

John from ProgrammableWeb shared a beer over visualizing complex integration systems. His team actually won an award once for a system that could visualize a complex integration solution consisting of messaging, file transfer, and many other technologies. His side links to a fun game GuessTheGoogle.

Martin taught me a new acronym: POX = Plain Old XML (as opposed to SOAP + WS-*)

hadoop.com is an open source map/reduce implementation.

Someone pointed me to BlueOrganizer - a Firefox plugin that allows the creation of semantically rich bookmarks that can be shared. For example, if you mark one of the supported sites (e.g. Amazon) the tool will bookmark the specific product (as opposed to simply the URL) and file it under the proper category (e.g., books, electronics).

Share:            

Follow:       Subscribe  SUBSCRIBE TO FEED

More On:  PATTERNS     ALL RAMBLINGS   

Gregor is an Enterprise Strategist with Amazon Web Services (AWS). He is a frequent speaker on asynchronous messaging, IT strategy, and cloud. He (co-)authored several books on architecture and architects.