My opinion is that SOA can be useful, at a macro level, but each service probably still will be large enough to need several internal components. The internal components may benefit from OO architecture. The SOA API should be defined more carefully than the internal APIs, since it is an external API. The data types … Read more
OAauth2 framework docs : https://www.rfc-editor.org/rfc/rfc6749 (A) The client requests an access token by authenticating with the authorization server and presenting an authorization grant. (B) The authorization server authenticates the client and validates the authorization grant, and if valid, issues an access token and a refresh token. (C) The client makes a protected resource request to … Read more
Forget about XML. Forget about WSDL. SOA is not a technology you can buy, though it’s often marketed that way. The real point of SOA is all about IT organization. The point of SOA is to avoid having a huge bunch of “applications” that have isolated data pools and either don’t talk to each other … Read more
Yes, repositories are generally used for queries only. Here is how I do it. The service layer manages the persistence. The controller layer knows of the service layer, but knows nothing of how the model objects are persisted nor where do they come from. For what the controller layer cares is asking the service layer … Read more
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
Here is a Typesafe/Reactive point of view on the question from Jonas Bonér. From the third paragraph of this blog post: The difference being that messages are directed, events are not — a message has a clear addressable recipient while an event just happen for others (0-N) to observe it.
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
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