Doorgaan naar hoofdcontent

SOA Design Patterns

Just like Design Patterns, Enterprise Integration Patterns and Architecture Patterns, Thomas Erl comes with a SOA Design Pattern book.
InfoQ has an interview with him: read interview

He states that a SOA patterns is something different than a webservice patterns. SOA is about services and a webservice is a technology specific realization of a service. He also states that in fact EAI frameworks and middleware, enterprise service bus platforms, grid computing, transaction management systems, messaging queues, event-driven messaging frameworks, broker and mediation technologies were used as inspiration for the SOA patterns.

He also explains his difference between service orientation and a SOA: "Service-orientation is a distinct paradigm that you apply to achieve a specific target state and a technology architecture is considered service-oriented if it has the characteristics necessary to support the application of this paradigm." Nice and clear right?

I have not read the book (yet), but I will come back to it. Hopefully it helps to answer when a service is a service. Does it have to have business value, or can secondary business functionality like HRM services also be considered services?
Labels:

Reacties

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h
12 reacties
Meer lezen

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
47 reacties
Meer lezen

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin
5 reacties
Meer lezen