Service Oriented Architecture

The UDDI API Sets

Tue, 10 Jun 2008 19:46:00 GMT

The UDDI API Sets

In my previous SOA post I covered the UDDI Information model in a fair amount of detail. While describing the UDDI Information Model I stated that the UDDI specification standardizes two aspects of SOA Metadata. These two aspects are the Information model and the way that the information model is accessed and manipulated. In this post I want to cover this second aspect of UDDI which deals with accessing the UDDI Information Model.

The UDDI Information Model

Sat, 26 Apr 2008 14:49:00 GMT

The UDDI Information Model

In my previous post I defined UDDI at a high level and provided a brief history of UDDI. I called out that UDDI standardizes two aspects of SOA Metadata. First it declares an information model using XML schema which is to be used as a standard way to represent SOA Metadata. Second, UDDI declares a collection of web services which are to be used as a standard way to access and manipulate the data represented by the information model. In this post I wan

A Brief Overview of UDDI

Fri, 14 Mar 2008 23:38:00 GMT

A Brief Overview of UDDI

In this post I want to take a high level look at Universal Description, Discovery and Integration (UDDI). Specifically I want to describe what UDDI is in non technical terms. I also want to provide a brief history of UDDI because UDDI has an interesting past. Finally, I’ll outline what I believe to be the benefits of UDDI.

The SOA Registry and Repository

Thu, 28 Feb 2008 14:48:35 GMT

The SOA Registry and Repository

In my previous post on SOA Governance I used the terms Registry, Repository, and System of Record in many of the figures that depicted Design time governance and Run time governance. These terms are often used synonymously in the software industry; however, they all evolved from distinct sets of capabilities.

Automating SOA Governance

Thu, 28 Feb 2008 02:31:21 GMT

Automating SOA Governance

In my last post I talked about SOA Policy and the value of having SOA Policy declared electronically. In this post I’ll pick up where my discussion of policy left off. Specifically, I’ll define governance and take a look at what it takes to apply governance in an automated fashion to an environment running services.

Defining SOA as an Enterprise Architecture

Sun, 03 Feb 2008 20:40:39 GMT

Defining SOA as an Enterprise Architecture

The term Service Oriented Architecture (SOA) is used to describe a variety of very different architectural patterns for using services. This is unfortunate because a term with more than one meaning is a term which causes confusion. Let’s look at a couple of definitions of SOA and make some observations about each.

Metadata for an Enterprise SOA

Sun, 03 Feb 2008 20:40:39 GMT

Metadata for an Enterprise SOA

In my previous post I asserted that today the best way to think about SOA is to think of it as an Enterprise Architecture. Specifically, if an organization wishes to maximize reuse and make sure that all their services are well behaved and operational, then information will need to be stored and maintained such that all services are well known and capable of being managed.

The Value of SOA Policy

Sun, 03 Feb 2008 20:40:39 GMT

The Value of SOA Policy

In this blog post I would like to investigate SOA Policy at a conceptual or logical level. I would like to keep this investigation conceptual so that the value of SOA Policy can be understood. It is easy to lose site of the value of SOA Policy when you start digging into the details of WS-Policy and other related standards which are used to implement SOA Policy. Furthermore, with the proper tools, development teams should never have to deal directly with these standards.