> Issue LXII, May 2012
Download Issue
Download Full Service Technology Magazine PDF

Consistency Patterns: Chemistry of ACID and BASE

Roger Stoffers

Roger Stoffers

Consistency patterns are solutions to the problem that a system must represent views and logic on consistent underlying data, but that that same data, while in the process of being changed, can temporarily be inconsistent. Most of us know that ACID and BASE are 'opposites', at least in the chemical world. In the IT world they are mechanisms with similar goals, but they achieve their goal in a completely opposite (or at least different way) with potentially different end results. It is vital that they not be confused with each other as they are distinctly different. ACID and BASE can be used complementary, comparable to the chemical world. ACID and BASE are used in the centrally coordinated aggregation of activities where each is intended to implement a specific way of consistency-control. Composition uses transaction commit and rollback (ACID) and orchestration uses compensation activities (BASE).

Driving from Business Architecture to Business Process Services

Hariharan V. Ganesarethinam

Hariharan V Ganesarethinam

Enterprise architecture (EA) is a strategic approach of defining an effective IT strategy and roadmap that drives the IT to meet the business vision and strategy. However, it is mandatory for enterprise architecture to have existing business architecture and IT architecture for preparation; it can be used to identify the gap in order to make strategic decisions and directions. Service-oriented architecture (SOA) and business Process management (BPM) architecture models will help an enterprise to realize the enterprise architecture strategy and roadmap. The perfect mixture of EA, SOA and BPM make enterprise IT highly agile so it can quickly accommodate dynamic business strategies, alignments and directions. However, there should be a structured approach to drive enterprise architecture to service-oriented architecture and business processes. Enterprise architecture is exclusively adopted by many enterprises to effectively plan and implement enterprise IT transformations. In order to prepare the enterprise’s IT for transformation requires various architectural models to represent various business models, workflows, processes, systems and

SOA Analysis within the Department of Defense Architecture Framework (DoDAF) 2.0 – Part II

Dawit Lessanu

Dawit Lessanu

We will begin by discussing in greater detail the purpose of each particular model and how it aids in service-oriented analysis. The following table relates service-oriented analysis to the respective DoDAF viewpoints that help with defining and scoping our overall SOA activities. The enterprise architecture scope is typically much larger in scope than typically considered in traditional service-oriented analysis. However, EA certainly can provide a wealth of information, proper context and well-defined boundaries for an effective service-oriented analysis. EA activities closely parallel those of service-oriented analysis. Using the models described above as guidelines, the following table discusses the relevance of specific DoDAF models to service-oriented analysis in greater detail.The AV and CV viewpoints provide a broad contextual backdrop to the SOA architect. The OV scopes the activities at a high level and identifies organizations and performers that have a stake in the outcomes of both the enterprise architecture activities and service-oriented analysis. The OVs are developed early in the EA and service-oriented analysis phase and are critical models leveraged in the subsequent steps. Due to the relationship between many DoDAF viewpoints, it is critical...

2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006