Search Results
Posted under EA on August 23rd, 2010 by Kyle Gabhart
The Open Group Architecture Framework (TOGAF) refers to it as architectural partitioning and the Federal Enterprise Architecture Framework (FEAF) describes it as architectural levels, but the effort of carving up Enterprise Architecture (EA) into multiple strata and then aligning those strata together as a part of a cohesive enterprise vision is an important element of […]
Posted under General on August 22nd, 2010 by Kyle Gabhart
For the past several months I have been a bit distracted and I have not made this blog a priority. There are several reasons for that:
I got married (January 1st).
I doubled the number of children living in my house when I did so (we have 6 between the two of us) .
I got swamped by […]
Posted under Cloud on February 2nd, 2010 by Kyle Gabhart
Over the past 6 months I have been working with a lot of clients that are either exploring the potential of Cloud Computing, or actively engaging in Cloud initiatives. As I have worked with these organizations and had countless whiteboard discussions with curious individuals, I have noticed some very common misconceptions regarding Cloud Computing.
Myth #1 […]
Posted under SOA on March 3rd, 2009 by Kyle Gabhart
Recently, a client approached me with a quandary. When designing XML schemas for Web services, how do you balance the desire to use industry standards such as UBL ( Universal Business Language) or CICA ( Context Inspired Component Architecture) to support data interoperability with the unique needs of particular domains and sub-systems within the enterprise? […]
Posted under Cloud on February 18th, 2009 by Kyle Gabhart
You and your team have had your heart set on achieving scalability, availability, reliability, and economical efficiency for some time now. Over the years, you’ve tried everything you can think of to achieve these goals.
A Journey of False Starts
This is not the first time you’ve had your heart set on revolutionizing your information systems:
One year, […]
Posted under SOA on December 4th, 2008 by Kyle Gabhart
In a previous post I blogged about the strong synergy between SOA and MDM. More recently, I explored the subject of service oriented data modeling (part 1 of this post) and how to resolve the inevitable conflicts that arise between your SOA view of data and your enterprise or MDM view of data. In this […]
Posted under SOA on December 3rd, 2008 by Kyle Gabhart
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 […]
Posted under SOA on November 5th, 2008 by Kyle Gabhart
Master Data Management (MDM) and Service Oriented Architecture (SOA) share common principles. The driving forces that lead organizations to adopt MDM and SOA are quite well aligned, resulting in a rather natural synergy. Consider the following principles:
Reusability
A primary driver of MDM is to allow applications to share data safely and avoid duplication.
SOA heavily promotes […]
Posted under SOA on September 26th, 2008 by Kyle Gabhart
In the most pure and simple service oriented scenario, a single consumer interacts directly with a single service provider.
For more complex situations, intermediaries are used to provide additional capabilities:
Security
Transactions
Routing
Data Mapping
Interface Mapping
Reliability
Protocol Translation
And etc…
What exactly is an intermediary?
An intermediary is a piece of hardware or software that bridges the gap between a service provider and service […]
Posted under SOA on July 22nd, 2008 by Kyle Gabhart
The structure of data for your service operations is very important. This is the primary way that information is transmitted within a service oriented environment. Moreover, the data model that you use for services will largely dictate service compatibility, interface flexibility, and to some degree will determine the extent of interoperability challenges that you will […]