InfoQ Homepage Architecture Content on InfoQ
-
Incorporating Enterprise Data into SOA
The majority of today's SOA design techniques are centered around definition of services. They use service-oriented decomposition, based on the business processes, enterprise business/functional model, required long term architectural goals and reuse of the existing enterprise functionality. This article takes a more data centric approach...
-
Railway Story: SimpleTicket
A 5-year old, Dallas-based company named Spur is gaining attention and kudos within Ruby on Rails circles. Earlier this week it announced a new release of its popular GPL'd IT support tool named SimpleTicket. Managing Partner Alexander Muse was kind enough to share the story of SimpleTicket with InfoQ.
-
ESB Alternative - Article removed at the author's request
This article was removed from InfoQ at the author's request.
-
Spring.NET - QnA
InfoQ had a chance to sit down with Aleksandar Seovic and Mark Pollack the co-creaters of Spring.NET. Spring.NET is an application framework that brings AOP, a Dependency Injection container and data access framework to .NET. It is not a complete port of Spring to .NET yet it preserves the tenets of Spring.
-
Adopting Agile Development Practices: Using Patterns to Share our Experiences
Agile adoption often proves challenging. Participants at a recent OpenSpace event focused on the dynamics of adoption rather than the structure that results from adoption. The resulting patterns are part of an effort to compile Agile adoption patterns answering: "What specific practices should I adopt?", "How can I adopt incrementally?" and "Where can I expect pitfalls?"
-
SOA Programming Models
Author Boris Lublinksy provides an overview of the dominant programming models that are emerging in the SOA domain including Windows Communication Framework (WCF), Java Business Integration (JBI) and Service Component Architecture(SCA).
-
Migrating to Struts 2 - Part II
In this part of the Struts 2 migration series, Struts committer Ian Roughely looks at a real application and compares the Struts and Struts 2 implementations, identifies how to convert actions, configuration changes, and what parts of the codebase don't need to be converted.
-
Do Agile Practices Make it an Agile Project?
Use of Agile methodologies is growing, but this comes with its own challenges: including the possibility of dilution as teams copy practices rather than growing them, implementing them without understanding. Perhaps it's time to talk about how failure to teach the basics puts much at risk: the integrity and engagement of team members, and the trust of their customers.
-
Using SEDA to Ensure Service Availability
A new strategy for incorporating event driven architecture for scalability and availability of services in the context of SOA. These strategies are based on queuing research pioneered for the use of highly abailable and scalable services, initially in the Web context, but moving into the SOA and Web services context. Actual implementation is described in the context of Mule.
-
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.