microservices

问题 I'm trying to set up environment for microservices. I'm using fabric8 to do that. I'm using mvn fabric8:cluster-start -Dfabric8.cluster.kind=openshift command. while executing i'm getting following error... [INFO] gofabric8> Downloading https://github.com/openshift/origin/releases/download/v1.3.1/openshift-origin-client-tools-v1.3.1-dad658de7465ba8a234a4fb40b5b446a45a4cee1-mac.zip... [INFO] gofabric8> **Unable to unzip /Users/apple/.fabric8/bin/oc.zip zip: not a valid zip fileUnable to

问题 The main benefit of Microservices are one Service “Type” can be scale out by using multiple container instances and load-balancing to improve through put. But one things is, multiple instances (ie. containers) of a "Service Type" are sharing the same database instance; and this could leave to performance bottle neck when multiple instance write/read on that database instance. Traditionally, we would scale up on the processing power of that database instance to meet high demand. The main

问题 I am still trying to find my way around micro-services. I have a fundamental question. In an enterprise scenario, micro-services would probably have to write to a persistent data-store - be it a RDBMS or some kind of NoSQL. In most cases the persistent data-store is enterprise grade, but a single entity (ofcourse replicated and backed up). Now, let's consider the case of a single micro-service deployed to private/public cloud environment having it's own persistent data-store (say enterprise

问题 This question stems from this other question I had asked about too many interfaces, QCRS and Mediatr library (request/response) Mediatr: reducing number of DI'ed objects I have created bunch of commands and queries and I have bunch of behaviors and one of them being is a Cache behaviour that for every query, cache is checked for the value before the query is actually executed against the db. So far this is working great, but the delima comes in when I have an UpdateSomethingCommand, once I

问题 I have a legacy application with a database that splits up the data into multiple schemas on the same physical database. The schemas are identical in structure. I use a microservice using Spring Boot Data JPA to do work on a single schema. Then to avoid code repetition, I created a router service that forwards the request to the single schema microservice replica each with a different database connection. But I found that a bit overkill (but works) I am trying to reduce it back down to a

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed last year . We are moving towards developing a web app in a micro-services architecture. We thought about running the services behind a API gateway that will handle authentication and will proxy the requests to the appropriate services. We have encountered a problem while setting up the

问题 I have a few microservices, which are exposed through an API-Gateway. The gateway takes care of handling authentication and routing into the system. The services behind the gateway are mostly simple CRUD-Services. Each service exposes its own API and they communicate synchronously via HTTP. All of these services, including the API-Gateway, are "default" NestJS applications. Let's stick with the Cats example. Whenever the Cat-Service updates or creates a new Cat , I want an CatCreatedEvent or

问题 I would like to avoid duplicating my POJOs in a microservices application, so I am wondering if there is a way to do that (like proxying)? I mean, is there a way for a Service A to access POJOs (or other classes/interfaces) defined inside a Service B without physically creating these POJOs classe files in Service A ? The big big challenge in a microservice architecture is that point and I didn't find a way to solve it. 回答1: "Simple": when there are two services that should be using something

问题 I am trying to make a simple Spring Boot web app using Microservice Architecture . I have two microservices with entities as defined below: Microservice 1 : @Entity public class Article { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; private String title; private String Content; } and Microservice 2 : @Entity public class Tag { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; private String title; } Now I want to have a Many To Many relation

问题 Helm is advertised as pretty much "the way to manage the deployment of apps on k8s". We have microservices whith a 1-to-1 mapping of code repo and deployable, and I would find it much more convenient to have the k8s config map along with the code, so that they evolve together, e.g. when adding a new environment variable for a feature flag. However, we maintain instead a single helm charts git repo, that would need to be occasionally updated in sync with the code. What is the best practice: