Quoted: In this interview, recorded at QCon San Francisco, (then) Burton Group consultant Pete Lacey talks to Stefan Tilkov about the reasons for his disillusionment SOAP and his opinions on how to best achieve loose coupling. Pete also describes the ideas behind REST, and addresses some of its perceived shortcomings. Finally, he discusses cases wher SOAP/WS-* or RESTful HTTP might be more appropriate.

Quoted: During OOPSLA 2007, InfoQ interviewed Markus Voelter asking him about creating software architecture documentation. Many people mention UML when they are asked about software design documentation, but Markus has a different take on that. He thinks that we should be using models which can be processed with tools which can validate or invalidate them.

Quoted: The latest release of GemFire - an in-memory data management product - offers distributed event processing capabilities with the introduction of continuous querying and durable event notifications as well as other new features. InfoQ discussed with Jags Ramnarayan, Chief Architect at GemStone, about these new features and the product's roadmap.

Quoted: Distributed Version Control Systems: A Not-So-Quick Guide Through

Quoted: Composite Software offers a new level of granularity when compared to SaaS (Software as a Service). Composite Software is about enabling "right-sourcing", i.e. move (or keep) arbitrary small or large elements of functionality wherever it is the most cost effective to operate them, not just entire systems. Economically, "right-sourcing" is far more efficient than "outsourcing" and SaaS. The goal of this book is start by understanding today’s software construction processes and technologies and explore why and how it should be evolved to support core composition mechanisms.

Quoted: After asserting that one must, as a rule, always version their database work, Scott Allen detailed an approach to making the best of versioning databases. Allen presented a comprehensive, practical approach to creating a baseline, using change scripts to manage schematic revisions, controlling programmatic database objects, and handling branching and merging.