Kyle Gabhart

We talk about Enterprise Architecture (EA) and Solution Architecture (SA) so much that sometimes I think we have ourselves convinced that it is actually possible to implement one.  We craft models, generate elaborate diagrams, and implement sophisticated tooling, all in the name of evolving our businesses and organizations through strategic EA and tactical SA. Don’t get me wrong.  I’m a strong believer in investing in EA and SA.  But I think it’s important to realize that you can’t deploy either one!  The only thing that you can possibly deploy into a production environment is Technical Architecture (TA).  EA is decomposed into one or more SAs, which are further decomposed into multiple TAs (see Figure below). At the end of the day, the only you can deploy is a new business process, data storage mechanism, software application, sub-system, equipment, etc. at the TA... (more)

Wireless Web Serviceswith J2ME Part IISOAP or XML-RPC? The answer depends on your needs

Last month in Part I (WSJ Vol. 2 Issue 1) we discussed J2ME and accessing Web services from wireless devices using the XML-RPC protocol. In this article, we will consider SOAP as a vehicle for accessing Web services from wireless devices, comparing and contrast-ing it with XML-RPC. Our sample application will again be a J2ME midlet, however, we will use EnhydraME's kSOAP rather than kXML-RPC to provide the protocol's implementation. Overview of SOAP The Simple Object Access Protocol is, according to the 1.1 specification, "a lightweight protocol for exchange of information in a de... (more)

SOA Governance: Start Small and Build Incrementally

If governance were a house, you would be left with the options of either building it from the ground-up or attempting to haul a complete house in on a large truck. While the latter is possible, it is fraught with difficulty. The house does not lend itself well to transport. It may become damaged during the move. It may not fit on your lot or connect smoothly to your utilities, requiring modifications to be made on the spot. The former option, building the entire house on site, certainly has its challenges (proper design, accurate implementation, quality assurance), but the risks ... (more)

Book Excerpt: Enabling Agile Business with SOA

This content is excerpted from Service Oriented Architecture Field Guide for Executives (978-0-470-26091-3) with permission from the publisher, John Wiley & Sons. You may not make any other use, or authorize any others to make any other use of this excerpt, in any print or non-print format, including electronic or multimedia. SOA Value Story Ronald Schmelzer, of industry think tank ZapThink, describes four key benefits to SOA.[1] Reducing integration expenses (both development costs and maintenance costs) Increasing asset reuse (no need to re-invent the wheel each time) Increasin... (more)

Which Came First, the SOA or the Data Model?

Recently I have been engaged in two Master Data Management (MDM) initiatives within the context of a larger Service Oriented Architecture (SOA) adoption plan. In both cases, the client found themselves at an impasse regarding how to resolve conflicts between the master data model and the data model required for one or more SOA artifacts (i.e. business process, service interface, etc.). Each client approached the problem from a different direction, but the conflict was essentially the same. Who wins and gets to run with their view of enterprise data? The MDM team or the SOA team? ... (more)