InfoQ Homepage Architecture Content on InfoQ
-
The Lost Art of Separating Concerns
In a short article, well-known REST proponent Mark Baker claims the default, Web services-based approach to SOA development fails to properly separate concerns, and describes how the more generic interface used in Web architecture leads to an improvement.
-
Interview: Using Agile for SOA
Recently, Digital Focus documented their experience using Agile to tackle SOA for Federal Home Loan Banks. The incremental approach included adopting an SOA platform that could grow as the SOA application portfolio grew, and getting frequent feedback from customers and developers. InfoQ interviewed both the client and the author of the experience report on the project, and business-IT alignment.
-
Casestudy: IP Telephony Integration
This case study takes at Litescape's IP telephone integration solution, from requirements through an architectural overview of their Java and .NET implementation, and then zooming in some interesting technical aspects of their project including phone integration with WebEx/LiveMeeting, integration between Java/.NET interop, HTTP vs. IPC communication between systems installed on the same machine.
-
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.