InfoQ Homepage Best Practices Content on InfoQ
-
Implementing SOA Governance
In this article, Todd Biske, an Enterprise Architect working for a F500 company, provides his guidance to implement a successful SOA Governance organization. He recommends a 3 step process focused on policy definition and enforcement. He also provides his perspective on the role of a SOA Center of Excellence with respect to Governance.
-
Business Processes for SOA Governance
Prabhakar Mynampati, an Advisory Architect at IBM, published last week an article detailing 6 SOA Governance business processes. The article includes a BPMN-like process definitions, rationales and benefits of adopting more formal approaches to SOA Governance.
-
The Power of Done
Scott Schimanski recently added his voice to those talking about the power of a clear definition of "done." Scott points out there is both business and personal value in a well-defined meaning of "done". The business can count on shipping features that are done, without making any additional investment, while individuals really seem to enjoy the sense of accomplishment that comes with "done."
-
What are the Qualities of a Good Test?
What is a good test? How do we know if we're writing good tests? Kent Beck, Roy Osherove, Mike Hill and others provide some insight.
-
Article: 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.
-
The Book of Architecture Axioms
"97 Things Every Software Architect Should Know" - a new community driven wiki that aims to provide bite-sized chunks of good advice.
-
Improving Web Service Security: Guidance for WCF
Microsoft patterns and practices group has released a WCF Security Guide. The 689 pages compendium offers a general introduction to Web Service security fundamentals as well as in-depth knowledge about several security threads and appropriate counter-measures.
-
Windows Communication Foundation: Application Deployment Scenarios
Microsoft has just published an excellent overview of WCF capabilities and deployment strategies for 5 most common SOA scenarios including Enterprise Web services, Web 2.0 services, intranet applications, queued messaging and Workflow services.
-
Mocking Web Services
Service simulation (mocking) – the ability to mimic service behavior even before they are implemented - enables service consumer developers and testers to parallelize their efforts without having to wait for service implementation to complete. Service simulation also provides a light-weight alternative to building expensive reference environments.
-
The State of Enterprise Architecture
As organizations continue to grow their IT investments (bought, borrowed, or built) and concepts like Business Process Management and Service Oriented Architecture become more common, the role of Enterprise Architecture (EA) has become more common. Recently, several people in the EA community have spoken about its current state.
-
Article: Software Development Lessons Learned from Poker
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? In this article, Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
-
The Semantic Web and Ontological Technologies Continue to Expand
Ontologies and Ontological management have become more popular as enterprise architecture has gained ground in organizations. As tool support has become available and the semantic and ontological concepts are being understood, more players, like the UMBEL project, the AKSW group, and consultant Dan McCreary have come to the table with contributions.
-
Agile Version Control for Multi-Team Development
Many agree that the minimum set of Agile practices includes disciplined version control. In particular, when several development teams work in the same codebase, to ensure there's a clean, releasable version at the end of every iteration, they need a plan. Henrik Kniberg's proven scheme is a useful guide for teams. This detailed paper includes the entire method and even a cheatsheet.
-
Presentation: Steve Jones on "Driving IT from the Business"
In a presentation recorded at QCon London, Cap Gemini's Steve Jones explains his concept of a business service architecture. Topics covered include how to apply SOA to existing systems, the problems one runs into when SOA is driven by technology, and the structural and organizational impact of business-driven SOA.
-
First (Forgotten?) Rule Of The Retrospective: Follow Through
Even the very greenest of agile teams clearly recognize the word 'Retrospective'. But, alas, it is often overlooked that a retrospective may be a wasted effort if not used to initiate an actual improvement that the team follows through on. Jim Shore gives advice on how to make the most of your retrospective and reminds us of the activity's ultimate place in the agile heartbeat.