What’s it take to be a Software Architect « Bobby Dimmick – Pragmatic Architecture Today on twitter, I noticed the following tweet fly-by: It struck a chord with me. A few years ago I got into an interesting conversation with a Security/Database Architect and a high level Systems Engineer regarding what it means to be a Software (or Systems or Enterprise) Architect. Long-story-short, the Engineer had been burned quite a few times by self-made Architects (think entrenched “Ivory Tower” Architects) while the Security Architect had actually met other Architects with passion, technical know-how, and the desire to truly develop value within their organizations.
Service Design Patterns - Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services
.netTiers Application Framework - .netTiers
AOP includes programming methods and tools that support the modularization of concerns at the level of the source code, while "aspect-oriented software development" refers to a whole engineering discipline. Logging exemplifies a crosscutting concern because a logging strategy necessarily affects every logged part of the system.
Atanu Banerjee Microsoft Corporation December 2006 Contents What Are Composite Applications?
It is wrong to assume that composite applications are by definition part of a service oriented architecture (SOA). Composite applications can be built using any technology or architecture. A composite application consists of functionality drawn from several different sources. The components may be individual selected functions from within other applications, or entire systems whose outputs have been packaged as business functions, modules, or web services. See also External links Composite application