InfoQ Homepage Architecture & Design Content on InfoQ
-
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.
-
Interview: Jim Johnson of the Standish Group
Jim Johnson, founder and chairman of the Standish Group, took time out from his vacation to talk with InfoQ editor Deborah Hartmann about his research, and the role of Agile in changing the IT industry. Johnson is best known for creating the CHAOS Chronicles: 12 years of independent research on project performance, including data on over 50,000 completed IT projects.
-
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.
-
Simplifying Enterprise Applications with Spring 2.0 and AspectJ
This article reviews Spring AOP support in 2.0, and walks you through an adoption roadmap for AOP in enterprise applications, with plenty of examples of features that can be implemented simply using AOP, but would be very hard to do any other way.
-
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.
-
Using Logging Seams for Legacy Code Unit Testing
Using logging seams you can easily create unobtrusive unit tests around legacy classes, without needing to edit class logic as well as avoiding behavior changes.
-
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.
-
Annotation Hammer
Annotations in Java 5 provide a very powerful metadata mechanism. Yet, like anything else, we need to figure out where it makes sense to use it. In this article we will take a look at why Annotations matter and discuss cases for their use and misuse.
-
Top 8 SOA Adoption Pitfalls
Thomas Erl is the world's top-selling SOA author. He has written two books on SOA. Understanding the pitfalls others have fallen victim to will help you chart a safer route down your own SOA roadmap. To this end Thomas has collected the eight most common SOA adoption pitfalls of last year.
-
ESB Roundup Part two: ESB Use Cases
This is the second part of InfoQ's ESB series, an exploration of Enterprise Service Bus, or ESB technologies. The focus is use cases required by companies deploying this technology, such as protocol bridging, security intermediation and service virtualization. The article references analyst commentary, survey research results and comments on part one of the ESB roundup.
-
Will the Enterprise change Ruby, or will Ruby change the Enterprise?
Ruby is often criticized for lacking the features required for developing large applications and maintaining them over long periods of time with large teams. Are we missing something fundamental for widescale adoption of Ruby in the enterprise?