William Martinez Pomares

Yep, my own. Although it may have some shared ideas, this is not a group agreement, nor the savior of what is now known as SOA (which is what is being done so far), nor something made for others to follow. It is just what I believe, what I follow, and what I teach each time I can. So, here it is. SOA MANIFESTO 1. Commons. a. SOA is an acronym composed of the words Service Oriented Architecture, which relates to an architectural style that is based on the rules of the service metaphor. b. A Metaphor is an application of the figure of speech concept to the IT design discipline. Using metaphors in architectural design actually refers to observing the rules of behavior of a particular entity in the business domain, and mimic them with an architectural element. c. A Service is conceived as a cohesive (and coherent) business functionality, technologically neutral, offered thr... (more)

A RESTFull WSDL?

In a recent comment, Paul mentions he is not familiar with the Document Style concept. This is a great opportunity to touch the theme and clarify some ideas about WSDL and the WSA idea of a service. WSDL is meant to describe the service definition and interaction models. WSDL defines: The Service’s visible endpoint. That is, the address where the port of the service leaves.The Binding. That is, which transport to use and how.The Operations. Each operation with a name and a message flow (a named message inbound or outbound). The Messages. Each named message has a number of named ... (more)

Notes on SOA Manifesto

In a recent discussion at InfoQ about the news of the upcoming SOA Manifesto, I had discussion with great people, including Jean-Jacques Dubray and Steve Ross-Talbot both renowned guys in the SOA world. We all talk the same, maybe at different levels or on different realms. Still, I promised Steve to put my two cents about SOA. Well, here I have a couple of ideas about it, too high level, but trying to clarify at least the three words that conform the acronym. Well, here they go. Many people talk about SOA and Services, but I’ve found in presentations, articles, case studies, wor... (more)

Longer Abstract for TSSJS presentations

DSL and Testing: using JSR in the Polyglot Architecture. Long ago, we started working with a Client, PushToTest, that has a tool for testing. The main idea of this tool was the ability to repurpose unit tests into functional, load and Monitor tests. It has also a proxy to record all transactions against a web page, so the transactions could be replayed later. At some stage, the intermediate language chosen to script tests and record the transactions was Jython. Over the years, it was learned that not all people knew Jython, nor Python nor Java. So, other scripts were added, adding ... (more)

Why Web Services Failed at SOA (and Why REST May Fail Too!)

First, let's review what is the concept behind services, with particular mention of the web services themselves. A service is a business functionality exposed by a simple interface. Note that it is not an object, nor a method, nor a module, not a procedure. It is pure business functionality. Services are consumed, not called, nor executed nor invoked. We define the service consumption as the interaction between agents, a client and a provider, which will communicate using a messaging system, where the data unit is a document. Consumption may be local or remote (meaning a service ma... (more)