microservices

SWIM protocol how does a new node get an address of an existing node in a cluster

跟風遠走 提交于 2021-01-29 04:10:43
问题 Background: I've been looking into microservices more specifically service discovery, one thing thats interested me is the SWIM protocol. But I'm a little confused when it comes to new nodes joining the network. How does a new node joining the cluster get an address of 1 or more nodes of the existing cluster, without their being a single point of faliure? If you need any further information or have any questions just let me know. 回答1: please check out scalecube that implements microservices

MICROSERVICES - communication between them

为君一笑 提交于 2021-01-29 02:40:17
问题 I've got one question concerning microservices architecture. I am designing a system based on microservices. I've read few articles and I think I understand the idea. However, I don't how microservices should communicate with each other while they have separate business responsibilities.... What I mean is that if I have a system for booking train tickets, I would divide backend application into modules: Client (login,logout,registration) Reservations (booking a train seat for user,getting all

Spring Boot app not working on Kubernetes cluster

て烟熏妆下的殇ゞ 提交于 2021-01-28 21:10:19
问题 I'm developing an application with microservice architecture using jhipster. I can run my services in dev mode even though i get this warning but when I run it on kubernetes cluster after i get this warning pod restarts itself over and over on loop. I have 4 microservies and a gateway. All the same. Thank you in advance. This is the warning: 2020-05-06 06:06:51.415 WARN 1 --- [scoveryClient-1] c.netflix.discovery.TimedSupervisorTask : task supervisor timed out java.util.concurrent

Is the facade design pattern only concerned with classes/modules or actual API calls too?

房东的猫 提交于 2021-01-28 14:00:51
问题 I think I understand the purpose of the facade design pattern- to provide an interface to a client that simplifies and abstracts a complex system allowing them to more easily perform a specific task. but the first thing I think of is a microservices style system that has many apis with each having a specific purpose and functionality. If I create another API (microservice) that makes calls on behalf of the client to a couple of the other APIs and abstracts the multiple APIs calls to just one

Is the facade design pattern only concerned with classes/modules or actual API calls too?

和自甴很熟 提交于 2021-01-28 13:58:40
问题 I think I understand the purpose of the facade design pattern- to provide an interface to a client that simplifies and abstracts a complex system allowing them to more easily perform a specific task. but the first thing I think of is a microservices style system that has many apis with each having a specific purpose and functionality. If I create another API (microservice) that makes calls on behalf of the client to a couple of the other APIs and abstracts the multiple APIs calls to just one

Is the Traffic between sidecar and main process encrypted in istio?

痞子三分冷 提交于 2021-01-28 09:41:02
问题 I know that istio supports mTLS for inter-service communication done through istio proxy but I couldn't find any documentation on their official site explaining the state of traffic between istio proxy container & main container itself in a pod ? (assuming it's a kubernetes managed cluster) Is the traffic encrypted between proxy and main containers ? If it's not by default, is there any config or plugin out there that can enable this behaviour ? Appreciate any help on this. 回答1: The traffic

Unable to fix veracode cwe id 918 flaw (SSRF) when using API gateway pattern in a Microservices architecture

ε祈祈猫儿з 提交于 2021-01-28 09:02:39
问题 I am using API Gateway Pattern in a Micro services architecture in which the Front End Angular app makes an HTTP request to my API Gateway project which is simply a ASP.net Core 3.1 Web API project. Currently I only have 2 micro services and an API Gateway and all of them are of type ASP.net Core 3.1 Web API project. The API Gateway project has all the controllers of my micro services . The purpose of the API Gateway is just to receive the request from Front end and make an HTTP Request to

Microservices: Worker roles, APIs or both?

你离开我真会死。 提交于 2021-01-28 03:27:39
问题 I have seen mixed examples of Microservices implemented as worker roles processing requests off a queue and/or as APIs (REST). Supporting asynchronous scenarios, a queue can be utilized, with a simple dumb queue listener forwarding the request to a Microservice REST API, where as synchronous scenarios would call the REST API directly. The term Microservice is vaguely defined I think; do people consider them APIs (e.g. RESTful services) or as any abstract service processing requests, however

JHipster support websockets in microservice architecture

落花浮王杯 提交于 2021-01-27 20:20:39
问题 I tried to implement websockets in one of the microservices in my project. However, I found out the Zuul proxy doesn't support websockets by default and jhipster developers is recommending adding websockets to gateway project as in https://github.com/jhipster/generator-jhipster/issues/7335 . Are there any better solution for this problem using a different proxy that will allow adding websockets to microservice? 来源: https://stackoverflow.com/questions/50679665/jhipster-support-websockets-in

Can the same dyno run multiple processes?

本秂侑毒 提交于 2021-01-27 11:43:08
问题 I am creating small app running multiple microservices. I would like to have this app available 24/7, so free dyno hours are not enough for me. If I upgrade to a hobby plan I would get 10 Process Types . Can I run another microservice on each of the processes (web), or does Heroku give me the ability only to install one web process per dyno, and the other 10 process types are for scaling my app? In other words, If i need 6 microservices running 24/7 should I buy 6 hobby dynos? 回答1: You can