InfoQ Homepage Architecture & Design Content on InfoQ
-
Quest for True SOA
Alex Maclinovsky explains why his vision of Governance differs from those prevailing in the industry. Based on his precise understanding of what a SOA platform should do, he defines a unified view of SOA Governance which he claims "has the potential to take the imperfect SOA platforms and implementations ... and transform them into true Service Oriented Architectures..."
-
Typemock: Past, Present and Future
In this interview with Eli Lopian of Typemock, he discusses the impetus for Typemock, it's differentiators and program futures. Typemock was originally created to fill a need for a Test Driven Development tool within the .NET community.
-
Using Ruby Fibers for Async I/O: NeverBlock and Revactor
Rails 2.2 is schedule to be thread safe - but will blocking I/O libraries make it necessary to run multiple Ruby instances? We take a look at how non-blocking I/O and Ruby 1.9's Fibers help solve the problem. We talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.
-
SOA Governance: An Enterprise View
SOA architect Michael Poulin explains the necessity for SOA governance to ensure an SOA initiative's success, and explains the role the OASIS SOA Reference Model and the accompanying SOA Reference Architecture assign to SOA Governance. Michael observes SOA governance specifics from the enterprise perspective and illustrates them with several examples of SOA Governance policies.
-
Scalability Worst Practices
In this article, former Orbitz lead architect Brian Zimmer discusses scalability worst pratices. Topics covered include The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.
-
Case study: Distributed Scrum Project for Dutch Railways
How we customise Scrum to our local context plays a large role in the success or failure of a project. This article describes a successful, large, distributed Scrum project, which had already been scrapped once under a traditional approach. The authors share lessons learned on: project startup, product ownership, testing and the importance of estimates and effective communication.
-
Silverlight and Java Interoperability
Robert Bell, Microsoft, introduces interoperability scenarios for using Silverlight from Java and provides architectural guidance using sample code snippets.
-
Book Review: Applied SOA
Applied SOA is a new book on Service Oriented Architecture written by 4 leading SOA practitioners that aims at making you successful with your SOA implementation. In particular, this book is going to help you tie your SOA initiative with your Enterprise Architecture, IT Governance, Core Data and BPM initiatives.
-
Comparing the Cloud: EC2, Mosso, and GoGrid
It was only recently that Amazon took cloud computing mainstream with the release of EC2. They are not the only game in town however. This new article takes a look at cloud server providers EC2, Mosso, and GoGrid.
-
8 Reasons Why Model-Driven Approaches (will) Fail
If you want to start building software in a model-driven way you’ll need to devise some methodology based on ideas and practical experiences from others. In this article, Johan shares with us 8 gotchas of Model Driven Engineering. The article contains a rich set of references to help you go further in your investigations.
-
Service-Oriented Development with Consumer-Driven Contracts
In this article, Ian Robinson discusses how "consumer-driven contracts", in the form of "stories for services" and unit tests exchanged between service development streams, can strengthen the service-oriented development lifecycle. In contrast to contracts defined from the POV of the provider, consumer-driven contracts result from combining the demands of all known service consumers.
-
Building Scalability and Achieving Performance: A Virtual Panel
Join our industry-heavyweight (eBay, Betfair, FiveRuns and Twitter) panel as they explore the cost of making their sites as scalable as possible, whilst tuning to get the most performance they possibly can. They explore the pros-and-cons of making their apps as awesome as possible - all the while under the pressure of their business requirements.