EL BLOG DE MODUS OPERANTIC

Todo sobre Integración de Sistemas, Interoperabilidad y Estrategia SOA

Service Statelessness

Service Statelessness

    Service Statelessness. Time for the sixth principle SOA: Service Statelessness.   SOA services should not save any information about session data, previous events, or previously reported service results. That is, the services must not have status.   Services must...
Service Autonomy

Service Autonomy

  Autonomy. It’s time for the fifth SOA principle: service autonomy.   Broadly speaking, this principle states that a service can not contain logic that depends on anything external to the service itself, be it a data model, an information system, or anything...
Service Reusability

Service Reusability

  Reusability. Time for one of SOA’s best-known principles: reusability. It is certainly one of the most obvious benefits of service orientation. It is surely the easiest to explain and understand. It is often the easiest to take on by those approaching SOA. In...
Service Abstraction

Service Abstraction

    Abstraction had to be in SOA principles. If you have read my previous entries in this blog, you will have seen how this concept often appears when we are dealing with service orientation. In fact we expressly dedicated this entry to this concept.   Abstraction....
Service Loose Coupling

Service Loose Coupling

  This second SOA principle puts focus on coupling, one of the main enemies to defeat through an SOA strategy. The goal is to achieve low coupling, as low as possible, and we will often talk about decoupling.   Loose Coupling In its statement promotes, as an objective...
Standardized Service Contracts

Standardized Service Contracts

Service Contracts. The first thing I would like to point out from this principle is the term Contract.   Do not make the mistake of thinking about the WSDL of web services. These contracts are located at the technological level. The SOA Service Contract is a design...
Página 2 de 41234