InfoQ Homepage Architecture & Design Content on InfoQ
-
Java + .NET, Integration Strategies Presentation
Ted Neward demonstrates using Microsoft Office to act as a rich client to Java, building a WPF gui on top of Java POJOs, and how to execute Java from within a Windows Workflow host.
-
How to Design a Good API & Why it Matters
Core Java language designer Joshua Bloch teaches how to design good APIs, with many examples of what good and bad APIs look like.
-
Secure and Reliable Web Services
Integration expert Guy Crets discusses how the WS-Security and WS-Reliable Messaging specifications can be used in real world integration and B2B scenarios.
-
Agile Quality: A Canary in a Coal Mine
Scrum co-creator Ken Schwaber spoke at Agile2006 on code quality as a corporate asset. In this video Schwaber discussed how a degrading codebase paralyses teams and increases corporate risk.
-
Introduction to Domain Specific Languages
Martin Fowler introduces a simple example of DSL, bringing out the difference between external and internal DSLs, and talking through the trade-offs in using both forms.
-
The Role of the Enterprise Service Bus
Mark Richards shares a detailed, product-agnostic vision regarding the role of an ESB and the capabilities an ESB must provide.
-
Architecting Toronto.com with ASP.NET
Toronto.Com attracts over 700,000 visitors a month. Built in 1997, the old technology was expensive and time-consuming to maintain. Scott takes us through what it took to modernize this site to .NET.
-
The Roots of Scrum
For 60 minutes Jeff Sutherland covers Scrum from creation to its use at Xerox, Honda, WildCard, Lexus, Google. He looks at Scrum types A, B C, and confirms that Kent Beck used Scrum practices for XP.
-
Agile Project Management Planning and Budgetting
Agile methods are empirical: plan, do, evaluate, plan again. To keep teams rolling, planning is critical. For 80 minutes David Hussman reviews practices for planning projects, releases, iterations.
-
AOP-Myths and Realities
Ramnivas Laddad tries to clear up the most common myths and misunderstandings that hinder the adoption of AOP discussing the reality [behind each myth] from an aspect-oriented-programming perspective.