Bick Group

David Linthicum

Subscribe to David Linthicum: eMailAlertsEmail Alerts
Get David Linthicum via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by David Linthicum

The transformation layer is the "Rosetta stone" of the system. It understands the format of all information being transmitted among the applications and translates that information on the fly, restructuring data from one message so that it makes sense to the receiving application or applications. It provides a common dictionary that contains information on how each application communicates outside itself (application externalization), as well as which bits of information have meaning to which applications. Transformation layers, such as those that process XML-based messages (e.g., XSLT), generally contain parsing and pattern-matching methods that describe the structure of any message format. Message formats are then constructed from pieces that represent each field encapsulated within a message. Once the message has been broken down into its component parts, the fiel... (more)

Joining Enterprises With Web 2.0

The notion of building bridges to service providers and managing the interaction will become more commonplace in 2006 as we learn to accept that many services we leverage within an enterprise are services we may not host. The technology exists today. We need to define and refine our approaches now, including architectures, enabling technology, and use of standards. Most enterprises are way behind. We are moving toward a day when most of our enterprise applications may be delivered as services, and thus provide a more economical way to approach information technology management w... (more)

Why 'Enterprise Architects' Are Ineffective with SOA

Architectures are like archaeology; in essence, layers upon layers of systems, applications, databases, and connections, typically built or procured to solve a tactical problem. Many corporations talk a good game and brag about the strategic long-term direction of the enterprise architecture that serves the business. The fact is, tactical needs have trumped strategic direction over the years. Thus, layers upon layers of technology on top of technology are the end result, and an architecture that is inflexible, static, fragile, and thus difficult to change along with the business... (more)

The Value of Inter-Domain Infrastructure Technology for SOA

In my recent predictions for 2009, I pointed out:   "There will be a larger focus on inter-domain SOA technology, or highly scalable and secure middleware technology that will provide scalable service and information access between the instances of SOAs within the enterprise, and perhaps intercompany as well. The fact is that much of the SOA solutions out there can't scale much past a single problem domain, thus this technology will become key to the strategic success of SOA." As SOA moves from the project level to the enterprise, SOA architects and practitioners quickly realize ... (more)

Understanding Coupling in the Context of an SOA

Since the beginning of computing we've been dealing with the notion of coupling, or the degree to which one component is dependent on another component in both the domain of an application or an architecture. Lately, the movement has been towards loose coupling for some very good reasons, but I'm not sure that many architects out there building SOAs understand the motives behind this. Breaking this concept down to its essence, we can state that tightly coupled systems/architectures are dependent on each other, thus changes to any component may prompt changes to many other compon... (more)