You trouble is how model your microservices. In term of microservices the second approach is most appropriate, which expose its logic through API. Always when you model your microservices keep in mind the follow facts. Loose Coupling: When services are loosely coupled, a change to one service should not require a change to another. The … Read more
Messaging tends to concentrate on the reliable exchange of messages around a network; using queues as a reliable load balancer and topics to implement publish and subscribe. An ESB typically tends to add different features above and beyond messaging such as orchestration, routing, transformation and mediation. I’d recommend reading about the Enterprise Integration Patterns which … Read more
May not be “best practice” advice here… but based on real life needs and experience: we have distributed system, 60 boxes running each 10 clients all do task X, and they need to take the next task from a queue. The queue is being fed from one other “client”… We had used inter process communication, … Read more
Although ESB is based on messaging, it is not “just” messaging and not just a buzzword. So if you start with plain old async messaging, the early networks tended to be very point-to-point. You had to wire up (i.e. configure through some admin interface) each connection and each pair of destinations and if you dared … Read more
Disclaimer: most of this post is subjective. No attempt has been made here to strictly define anything, just trying to contextualize and give a global overview of the concepts and how they relate to each other. I thought I knew what REST/”RESTFul”, restfulservices, webservices, SOA and microservices I’d say that all these terms fall into … Read more
SOA main principles: Build systems as set of services where each service is Coarse-grained Interoperable Loosely coupled A company offers a lot of business services (coarse-grained) developed over many years and exposed to the users (human or other systems) in some form. There are more chances that each of these features have been designed and … Read more
I didn’t read the article, so I can only speculate what he can mean exactly, but as he gives ESB as an example against microservices and ZeroMQ as an example for micro services I hope my speculation will be pretty exact: One of the ideas of Unix (and Linux) is to build small independent applications … Read more
Are you integrating existing applications, or do you just want to support your own applications? Are you looking for actual SSO or simply shared credentials? SSO is logging in to a single application, and having that credential propagate to another application (such as logging in to Gmail and being automatically logged in to Blogger). Shared … Read more
Service Oriented Architecture is an architectural methodology. It is a way of specifying separation of responsibility from a business oriented point of view into independent services, which communicate by a common API (often but not necessarily by publishing events to a bus). As an example, you could have one service responsible for capturing customer orders, … Read more
An API Gateway is a proxy provided for the client. The Gateway gives the client a consistent interface regardless of any changes within the internal system. It allows the internal system to change without affecting the client. The API Gateway can also provide consistent cross-cutting concerns such as security logging, reporting and API analytics. An … Read more