InfoQ Homepage Articles
-
Are You a Software Architect?
The line between development and architecture is tricky. Some say it's fake, that architecture is an extension of the design process undertaken by developers; others say it's a chasm that can only be crossed by lofty developers who believe you must abstract your abstractions and not worry about implementation details. There's a balance in the middle, but how do you move from one to the other?
-
Agile – A Way of Life and Pragmatic Use of Authority
Vinay Aggarwal shares many instances in life where authority is needed and lack of authority allows for extremely costly mistakes. He then explicitly suggests where authority could and should be used in Agile environments.
-
Using ITIL V3 as a Foundation for SOA Governance
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. Based on their perspective, they would be correct since V2 focused more heavily on operational processes rather than service lifecycle. With ITIL V3, the focus of the framework shifted toward what can only be accurately described as service-orientation.
-
What's New in Two: Adobe AIR 2.0 is Coming Soon!
Adobe AIR 2.0 is coming, and it contains many highly requested features that application developers have wanted since AIR 1.0 was released nearly two years ago. When Adobe releases the new runtime, it will be automatically downloaded and installed by all of your users. It's important to test now to make sure you're not caught off guard. And, you can get a head start using some of the new features.
-
Agile and SOA, Hand in Glove?
Agile is the hand that works in the glove. SOA is the glove, the scope is enterprise wide. Most principles of SOA and Agile are not in conflict. When they are, they keep each other sane. Agile development without a clear vision of the goals and objectives of the company is futile. SOA without a clear vision how to make it real using agile development principles is a waste of time and money.
-
BlazeDS and JMS for PHP Developers, Part 1
BlazeDS is an open source project from Adobe that allows you to connect your Adobe Flex applications with data services. The Java Messaging Service (JMS) is a method of communicating with services written in Java. In the first of two articles, InfoQ looks at the advantages of JMS and how you can use BlazeDS to communicate with your Java services via JMS from your Flex applications.
-
The Meme Lifecycle
Julian Everett and Chris Matts describe an IT business case as a meme - one that is competing in the complex ecosystem that constitutes a market sector and show its implications. By taking this view of a business then an organization's short and long term strategies change and we get a completely different view of how and why current development practices exist and persist.
-
Resource-Oriented Architecture: Resource Metadata
In this second article in the Resource-Oriented Architecture series, Brian Sletten discusses the benefits of REST, what constitutes a resource, associating metadata with a resource, the pitfalls of common models of resource metadata, SPARQL, RDF, expressing RDF facts, RDF triples, querying RDF, and sample RDF queries.
-
mySOA: Agile, Governed and Sustainable
William El Kaim, Lead Architect at Carlson Wagonlit, provides a rare glimpse at all the choices, and the rationale behind them, he and his colleagues have made while building their organization's Service Oriented Architecture. How does your SOA compare? What will be the major evolutions in the next few years? How will the Cloud impact current SOAs?
-
Google Go: A Primer
Google recently announced their new programming language, Go. It is designed to bring some of the advances of modern programming languages back down to the systems arena where C still dominates today. However, the language is still experimental and evolving. This primer will help explain the intricacies and structure of the Go language for those who are interested in learning more about it.
-
Book Excerpt: Succeeding with Agile: Software Development Using Scrum
This is a book excerpt from Mike Cohn's new book "Succeeding with Agile: Software Development Using Scrum". This article describes the primary adjustments individuals must make as they transition from traditional roles to Scrum. The focus is on how these roles change, rather than on a thorough description of each role.
-
Agile Teamwork: The Leadership - Self-management Dilemma
Self-managed teams are unstable and are successful when the ‘Leadership – Self-Management’ dilemma is understood and dealt with. Too much central control destroys agility, inhibits creativity and resists change. Too much self-management leads to chaos and anarchy and destroys a team. A successful Agile Team operates as far along self-management as it can, without tipping over into chaos.