Dave Duggal explains Consilience's Ideate, a real-time application-integration platform for linking information in the enterprise. Dave explains the motivation, concept and technology behind Ideate.
Ganesh Prasad explains how the contribution of SOA is the management of dependencies between systems, how SOA is a design aspect and not a technological one, and much more.
Rob Daigneau talks about his book "Service Design Patterns" and the various patterns described in it, SOA vs Services, how to choose between REST, RPC and Messaging, and much more.
John Davies talks about standards based messaging and integration in the finance business, the future of payment systems and mobile payment, and much more.
In this interview done by InfoQ's Srini Penchikala, Oleg Zhurakousky talks about the cloud architectures with messaging as the core part of the cloud solutions. He also discusses the Spring Integration and other Spring projects like Spring Roo and Cloud Foundry.
Bob Ippolito talks about building web services with the Erlang-based MochiWeb and the differences to the Yaws web server, the strengths of Erlang and Python, and more.
Justin Sheehy discusses the benefits of RESTful web frameworks and how these apply to the Webmachine toolkit. He also talks about security, debugging and the future of web frameworks and HTTP.
In this interview, Subbu Allamaraju talks about real life issues of RESTful architectures. He also describes a pragmatic approach of adopting the Web as an integration platform and shares his opinion on OAuth.
Mule Creator Ross Mason discusses Mule's evolution over the years and what's new in Mule 3, as well as a new architectural pattern of using ESB's in the cloud. JSON as a data interchange format is discussed, as well as ESB's as a backend for mobile devices.
In this interview, Ryan discusses the components of the Salesforce.com architecture and how they achieve scale. They discuss the different cloud service models and the viewpoint of Salesforce as well as the history of their APIs including Force.com and their decision to move from SOAP API to a Rest-based API.