Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs. In this article, Ganesh Prasad and Peter Svensson explains how and why.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera. The authors spent the last year implementing an Atom Store for Homeaway, their employer, and are mnow making the Atom Store framework available as open source.
This article, based on a chapter from the book "Service Oriented Architecture Demystified", discusses the benefits of applying SOA to heterogenous environments in the healthcare domain. Focusing on a domain instead of technology perspective first provides an interesting view on the business motivation for SOA.
InfoQ spoke to the lead developers of the most important open source Java Web-services stacks about their design goals, standards, data binding, XML, interoperability, REST support, and maturity. 12
Today, almost every modern application consumes or produces XML. Stefan Bodewig explains the challenges in testing XML-based applications, and shows how to use the XMLUnit Java Framework to do so. 8
Ted Neward demonstrates how Office 2007 files can be read and written without anything more complicated than the native JDK itself. 25
InfoQ had a chance to talk to Frank Cohen about his FastSOA methodology and architectural patterns. We have also published a one-chapter excerpt from his book on the topic. 6
Rails makes it easy to support micro-format standards alongside XML in RESTful applications, potentially opening them up to a wider audience and/or reducing their bandwidth requirements. 1
In this article, Stefan Tilkov proposes 10 principles to serve as a basis for SOA discussions, focusing on abstract concepts that are independent from any particular vendor framework. 6
Spring Web Services creator Arjen Poutsma talks about Spring's WS stack and the different approach it has to building Java Web services. 7
.NET and Java interop can be made really simple using a REST document centric approach. This article demonstrates REST for interop as well as POST-REST. 4