Unless those micro-services are tightly coupled (meaning it wouldn’t make sense to download only some of them, and you would only work with all of them), keeping them each in a separate Git repo is recommended. But you can still reference them as submodule in a parent repo in order to keep track of their … Read more
It is possible to use a shared database for multiple microservices. You can find the patterns for data management of microservices in this link: http://microservices.io/patterns/data/database-per-service.html. By the way, it is a very useful blog for microservices architecture. In your case, you prefer to use database per service pattern. This make microservices more autonomous. In this … Read more
Microservices in my own, hopefully simple terms Monoliths Traditionally web applications are big. You write one piece of software that runs on a server and answers requests in form of HTML, XML or JSON. If you want your web application to do something new, you add that functionality to the existing application. Such big systems … Read more
I am going to implement the orchestration of a set of microservices in my application. This is a hard problem to solve by yourself. You are probably better off using an existing orchestration system (see below). Is there any other powerful tool? You should look into kubernetes, which seems to be the standard in orchestration … Read more
I find I have to add these two applications to the appllication.properties,it can work.Only one is not enough. eureka.client.register-with-eureka=false eureka.client.fetch-registry=false
Well, Reactive Programming means you are doing all your IO bound tasks such as network calls asynchronously. For an instance say your application calls an external REST API or a database, you can do that invocation asynchronously. If you do so your current thread does not block. You can serve lots of requests by merely … Read more
My take is do not use an in-container process supervisor (forever, pm2) and instead use docker restart policy via the –restart=always (or one of the other flavors of that option). This is more inline with the overall docker philosophy, and should operate very similarly to in-container process supervision since docker containers start running very quickly. … Read more
I’m not sure if what I am going to answer is thé right way. I’m still learning myself.. But I can tell you how I’ve implemented my microservices attempts.. First, I started with HTTP communication based microservices using this blog. This works fine, but the problem is, that you create dependendies between your services. Service … Read more
Definition 1: The direction of action Upstream: receiving requests from / sending responses to A service upstream is calling me. Downstream: making requests to / receiving responses from I am calling a service downstream. Definition 2: The direction of dependency Upstream: making requests to / receiving responses from I am calling a service upstream. Downstream: … Read more