Erich first gives us a general overview of Jazz, and then we discuss the motivations for Jazz, highlighting ways it aims to help geo-distributed teams and better document desires and explanations in code. We also talk about Jazz’s architecture: how it can be deployed as a whole, or taken part-by-part.
Next we get into a discussion of how to manage the “openness” of a project like Jazz, where-in Erich makes some interesting comparisons to the way Eclipse was developed early on. Tied up with this is a brief discussion of how thinking about commercializing the architecture enters general design thinking.
Rounding out the Jazz portion of the podcast, I ask Erich about the use of REST over SOAP (or other WS-* stuff) in Jazz.