At first, REST, RPC – architecture patterns, AMQP – wire-level and HTTP – application protocol which run on top of TCP/IP AMQP is a specific protocol when HTTP – general-purpose protocol, thus, HTTP has damn high overhead comparing to AMQP AMQP nature is asynchronous where HTTP nature is synchronous both REST and RPC use data … Read more
SOA is a new badge for some very old ideas: Divide your code into reusable modules. Encapsulate in a module any design decision that is likely to change. Design your modules in such a way that they can be combined in different useful ways (sometimes called a “family” or “product line”). These are all bedrock … Read more
Imagine you are developing a web-application and you decide to decouple the functionality from the presentation of the application, because it affords greater freedom. You create an API and let others implement their own front-ends over it as well. What you just did here is implement an SOA methodology, i.e. using web-services. Web services make … Read more
Basic technologies (such as XML, SOAP, WSDL) provide means to describe, locate, and invoke services as an entity in its own right. However, these technologies do not give a rich behavioral detail about the role of the service in more complex collaboration. This collaboration includes a sequence of activities and relationships between activities, which build … Read more
No matter whether or not you think about SOA as implemented by SOAP, REST or messaging, services are document-centric. Services are not object-oriented. While polymorphism is a strong design tool in OOD, it’s not applicable in SOA because SOA modeling doesn’t involve classes.
In this case I would not use the existing services in the Renewal Service, like you say they could change. I follow the principle that in SOA services should have a business meaning. I would therefore create a new operation: IsContractRenewalInProgress. This removes the need to think about who should be responsible for validating that … Read more
It sounds like you are trying to use SOA to remotely access your object model. You would be better of looking at the interactions and capabilities you want your service to expose and avoid exposing inheritance details of your services implementation. So in this instance where you need a list of user accounts your interface … Read more
The problem from what I can see is that SSRS violates the Contract Centralisation Pattern. Instead your report should be generated from either the services you have created, or by extending those services. Otherwise you create a tight technology based coupling between your report and your databases, which will make it more difficult to modify, … Read more
First of all – you need to understand if you really need full-blown SOA. SOA basically means that every operation is going through service that decouples our system from other system/s. In rare cases (in case application grows extra huge) – one part of system from another. Will your application “talk” with any other application? … Read more
My take to describe this in a more accessible way… In order to understand what Apache Camel is, you need to understand what are Enterprise Integration Patterns. Let’s start with what we presumably already know: The Singleton pattern, the Factory pattern, etc; They are merely ways of organizing your solution to the problem, but they … Read more