microservices

问题 I'm a little bit confused about the microservice best practice approach. Following scenario: Massive incoming messages from mqtt devices. A rest api where customers could read the messages (mostly only a part of them). My idea was, to create one microservice for storing the messages in a database table. And a second microservice with a rest api to read this messages. I want to do this, because of scaling issues. (The incoming storing part needs much more power, than the reading rest api) I

问题 Let's say I'm using an GCE ingress to handle traffic from outside the cluster and terminate TLS ( https://example.com/api/items ), from here the request gets routed to one of two services that are only available inside the cluster. So far so good. What if I have to call service B from service A, should I go all the way and use the cluster's external IP/domain and use HTTPS ( https://example.com/api/user/1 ) to call the service or could I use the internal IP of the service and use HTTP ( http:

问题 Let's say I'm using an GCE ingress to handle traffic from outside the cluster and terminate TLS ( https://example.com/api/items ), from here the request gets routed to one of two services that are only available inside the cluster. So far so good. What if I have to call service B from service A, should I go all the way and use the cluster's external IP/domain and use HTTPS ( https://example.com/api/user/1 ) to call the service or could I use the internal IP of the service and use HTTP ( http:

问题 I've read a post saying that: We can not implement traditional transaction system like 2 phase commit in micro-services in a distributed environment. I agree completely with this. But it would be great if someone here can explain the exact reason for this. What would be the issues I'm going to face if I'm implementing 2-phase commit with microservices? Thanks in advance 回答1: The main reason for avoiding 2-phase commit is, the transaction co-ordinator is a kind of dictator as it tells all

问题 I have installed a Kubernetes with Kubeadm tool, and then followed the documentation to install the Web UI (Dashboard). Kubernetes is installed and running in one node instance which is a taint master node. However, I'm not able to access the Web UI at https://<kubernetes-master>/ui . Instead I can access it on https://<kubernetes-master>:6443/ui . How could I fix this? 回答1: The URL you are using to access the dashboard is an endpoint on the API Server. By default, kubeadm deploys the API

问题 I'm dealing with an application using multiple microservices. The application receieves data and processes it, and I'd like to have a way to monitor everything the received data is going throughout the microservices. Since the platform is nodejs we're dealing with asynchronous processing, logs wont always be written one after the other, and since the data does not have aמ ID the logs cannot be filtered in any convenient way. Is there any way to track the data from the first moment it enters

问题 I have a monolithic application with single process having 5 threads. Each thread accomplishes certain specific task. Thinking to move this application to microservices using dockers. If I look at the architecture, each worker thread would become a docker process. So, in some way Monolithic vs Microservices becomes more like Thread vs Process discussion in my case. The original thinking of having the monolithic was to have threads for performance and share the same memory. Now with

问题 I have a monolithic application with single process having 5 threads. Each thread accomplishes certain specific task. Thinking to move this application to microservices using dockers. If I look at the architecture, each worker thread would become a docker process. So, in some way Monolithic vs Microservices becomes more like Thread vs Process discussion in my case. The original thinking of having the monolithic was to have threads for performance and share the same memory. Now with

问题 First of all, I'm using JHipster 4.0.x for my project. I'm using microservices architecture. For this example, I've got one gateway, one microservice for "Store" and a second one for "Skill". I want to centralise all Stores in one database and Skills in a second one. Each one is a data repository that will not evolve at the same speed. On the other hand, they will be the central point of my infrastructure in order to update, via an ESB, the other software. Jhipster is great for that, I've got

问题 First of all, I'm using JHipster 4.0.x for my project. I'm using microservices architecture. For this example, I've got one gateway, one microservice for "Store" and a second one for "Skill". I want to centralise all Stores in one database and Skills in a second one. Each one is a data repository that will not evolve at the same speed. On the other hand, they will be the central point of my infrastructure in order to update, via an ESB, the other software. Jhipster is great for that, I've got