InfoQ Homepage Architecture Content on InfoQ
-
9 Fallacies of Java Performance
Over the past 18 years Java has evolved into the premiere language of the enterprise. Yet cognitive fallacies persist about Java performance. In this article we examine some popular misconceptions.
-
The Seven Information Smells of Domain Modelling
Domain modelling is a powerful technique that many IT professionals have in their toolkit. Unfortunately a couple of issues with domain modelling have caused it to fall out of favour over the past few years, especially in Agile circles. Two real problems with the approach are that it takes too long, and that it is prone to “analysis paralysis”. This is an approach that addresses these issues.
-
Agile Software Architecture Sketches and NoUML
Understanding the software architecture of what you're building can prevent chaos and encourage collective code ownership. In the race for agility though, many teams struggle to do this, particularly since they've abandoned UML in favour of "boxes and lines" sketches. Moving fast requires good communication, but how do you do this without resorting to big design up front and UML?
-
Interview with Michael Azoff from Ovum about How To Create the Agile Enterprise
Large enterprises face three challenges: to innovate and act as a start-up, to use a budgeting process that keeps the organization’s strategy in touch with changing market conditions, and to transform the whole IT department to agile. Principal analyst Michael Azoff explains Ovum’s view on creating an agile enterprise.
-
The Real Question is Why?
The Agile movement has driven a revolutionary change in the way we build and deliver software solutions. In the past few years Agile frameworks have become mainstream. Agile has solved the problems of the 90's and early 2000's. Now a new kind of problem is emerging that needs an equally elegant solution, how do we build the right solution? Do we know Why we are building it?
-
Key Takeaway Points and Lessons Learned from QCon London 2013
This article presents the main takeaway points as seen by the many attendees who blogged or tweeted about QCon. Comments are organized by tracks and sessions: Keynotes, Distributed Systems / REST, The Java Developer Track, The Developer Track, Building for Clouds, Real Startups, Creative Thinking & Visual Problem-solving, Handheld Banking and many more!
-
Choosing the Right ESB for Your Integration Needs
Kai Wähner explains the differences between an integration framework, an ESB and an integration suite, following with advice for selecting the right one from existing commercial and open source solutions.
-
Capturing Compliance Requirements: A Pattern-Based Approach
Assuring compliance across an enterprise is critical and necessitates a holistic approach for defining a consistent set of process and system level controls. In this article, authors discuss a new pattern-based framework to capture and manage business process compliance requirements. They also talk about implementation of the framework and two case studies in banking and e-business domains.
-
How Would You Build Up a City from Components?
Aliaksei Papou explores how components and common design patterns such as the Observer and Finite State Machine make it possible to design an application such that it can grow and change according to your needs using the analogy of a house.
-
Application Performance Management Maturity Model
In this article, author Jim Hirschauer justifies the importance of application performance management (APM) process in organizations. He also describes a maturity model for application performance management with three different levels of maturity.
-
Evaluating Agile and Scrum with Other Software Methodologies
Historical data is a key resource for judging the effectiveness of software process improvement methods and also for calibrating software estimation accuracy. In this article, Capers Jones compares Agile and Scrum with a sample of contemporary software development methods using several standard metrics.
-
Growing EAI with Apache Camel
This article comprises practical examples of typical integration challenges and explores how Apache Camel can meet these challenges. These examples are presented in the context of an integration solution that starts simply but grows over time as new integration needs arise. The article concentrates on how Camel helps managing complexity and keeping the team productive.