InfoQ Homepage Architecture Content on InfoQ
-
Java, .NET, But Why Together?
The Java vs. NET war is over. In this article, Ted Neward looks at how we can leverage the strengths of each together, such as using Microsoft Office to act as a "rich client" to a Java middle-tier service, or building a Windows Presentation Foundation GUI on top of Java POJOs, or even how to execute Java Enterprise/J2EE functionality from within a Windows Workflow host.
-
Eric Newcomer on WS Transaction Standards
In a recent blog post, IONA CTO Eric Newcomer wrote about the OASIS Transaction TC's progress in standardizing the Web services WS-Coordination, WS-AtomicTransaction and WS-BusinessActivity specifications. Eric talked to InfoQ about this particular set of specifications, as well as the standardization process and the role of the big players in general.
-
Migrating Struts Apps to Struts 2
Struts committer Ian Roughely explains, from the perspective of a Struts developer, the high level architecture, basic request workflow, configuration semantics and differences in the action framework in the new Struts 2 (formerly WebWork). Armed with this knowledge, migrating an application of any size from Struts to Struts 2 should be simplified.
-
An Introduction to Web Services Reliable Messaging
Web Services Reliable Messaging 1.1 is available as a new draft version of the OASIS specification originally released by Microsoft, IBM, BEA and others. WS-RM ensures messages can be delivered reliable over unreliable protocols such as HTTP. Paul Fremantle, co-chair of the OASIS technical committee, provides an introduction.
-
An Update on Spring 2.0 Final
Spring 2.0 was initially supposed to come out in June/July, why the delay? InfoQ interviewed the Spring team - based on massive community feedback, the team has chosen to delay the launch to Sept 26th in order work on asynchronous JMS capabilities, JPA, the new JSP form tag library, OSGi integration, documentation, and backwards compatibility.
-
Agile Business Rules
James Taylor looks at the challenge that arises when the new requirements are not really requirements at all, but new or changed business rules. Aren't business rules the same as requirements? Taylor says: no, not really; and looks at how to make an agile development processes work just as well for business rules as they do for other kinds of requirements.
-
From Java to Ruby: Risk
"Ruby is risky" is a common perception. As Ruby on Rails moves closer to the mainstream, that risk will decrease. In this article, Bruce Tate examines the changing risk profiles for Java and Ruby from a managers perspective, examining Java's initial adoption and also common risk myths about Rails.
-
Give it a REST: Mark Baker on Web Services
Mark Baker is well-known in the SOA and Web services community because of his continuous efforts to promote REST (REpresentational State Transfer), criticizing many of the standards and specifications as being ignorant of what made and continues to make the Web successful. Stefan Tilkov had the chance to talk to Mark about REST principles, its benefits, and the relationship to Web services.
-
Web Services Guru Dr. Frank Leymann on SOA
Frank Leymann is a full professor at the University of Stuttgart and co-author of many Web Service specifications, including WSFL, WS-Addressing, WS-Metadata Exchange, and the WS-Resource Framework set of specifications. He was one of the driving forces behind BPEL4WS. InfoQ's Stefan Tilkov talks to Dr Leymann about SOA research, REST, Web Services and other important topics for SOA.
-
Why Would a .NET Programmer Learn Ruby on Rails?
.NET developer Stephen Chu gives us some insight into his transition to Ruby on Rails programming. Quote: "By being loyal to one technology stack, I am bound to unconsciously make biased decisions, which will ultimately hinder my ability to deliver business value."
-
Executive summary - An Adaptive Performance Management System
Traditional thinking has turned budgets into fixed performance contracts forcing managers at all levels to commit to specified financial outcomes, although many of the underlying variables are beyond their control. In this Cutter Executive Summary, Jim Highsmith offers an alternative for the adaptive organization: a project performance management system and a team performance management system.
-
Agile: The SOA Hangover Cure
Author Carl Ververs who is an expert on SOA Integration and Distributed Systems writes about the application of "Agile" development philosophies that ensures that organizations can overcome architectural paralysis and get moving on those important SOA projects, while at the same time ensuring that the architecture is sufficiently flexible and adaptable for future growth.