microservices

问题 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

问题 I have a multi-module maven project where the single modules are all runnable microservice applications containing their own Dockerfile, so in production every module will be a containerized application. The parent project, which contains the child-modules only contains the parent pom.xml and the docker-compose.yml I have tried to use the following Dockerfile (on sub-module level): FROM sgrio/java-oracle RUN apt-get update RUN apt-get install -y maven COPY ../pom.xml /usr/local/service

问题 I have a multi-module maven project where the single modules are all runnable microservice applications containing their own Dockerfile, so in production every module will be a containerized application. The parent project, which contains the child-modules only contains the parent pom.xml and the docker-compose.yml I have tried to use the following Dockerfile (on sub-module level): FROM sgrio/java-oracle RUN apt-get update RUN apt-get install -y maven COPY ../pom.xml /usr/local/service

问题 Working on migrating a huge monolithic application to microservices paradigm, needless to say the domains identification and mapping then to different microservices and the orchestration has been quite a task. Now as the previous application shared the master data in the same schema, in the new paradigm it gets difficult for me to manage that, my choices are: Replicate the same master data in each microservice: Pros: when cached in the application works fast and no looksup, application within

问题 I am facing this warning/error while forwarding the incoming http request to the downstream path. Ocelot.DownstreamRouteFinder.Middleware.DownstreamRouteFinderMiddleware: Warning: requestId: 80000025-0004-fd00-b63f-84710c7967bb, previousRequestId: no previous request id, message: DownstreamRouteFinderMiddleware setting pipeline errors. IDownstreamRouteFinder returned Error Code: UnableToFindDownstreamRouteError Message: Failed to match Route configuration for upstream path: /getDepartment,

问题 I'm currently developing a microservices architecture in NodeJs. My first approach, was a package.json per service. Although, it can be very tricky when accessing to a common area (with logging or database utils), for all microservices. For instance: common-area > logger.js package.json - install module typeorm service1 > app.js - use logger.js package.json - also install module typeorm When running node app.js (Service 1) we end up with 2 typeorm modules loaded, once we made two different

问题 I'm currently developing a microservices architecture in NodeJs. My first approach, was a package.json per service. Although, it can be very tricky when accessing to a common area (with logging or database utils), for all microservices. For instance: common-area > logger.js package.json - install module typeorm service1 > app.js - use logger.js package.json - also install module typeorm When running node app.js (Service 1) we end up with 2 typeorm modules loaded, once we made two different

问题 I'm currently developing a microservices architecture in NodeJs. My first approach, was a package.json per service. Although, it can be very tricky when accessing to a common area (with logging or database utils), for all microservices. For instance: common-area > logger.js package.json - install module typeorm service1 > app.js - use logger.js package.json - also install module typeorm When running node app.js (Service 1) we end up with 2 typeorm modules loaded, once we made two different

问题 I am developing a multi-container app in docker. One of the services is a long-running console application in C# which basically does some polling on a database and sending the data to e server. I just keep the service running by adding this statement: while(true); Now I'm thinking of changing this service to a .NET Core worker service (or even windows service, since I am only using windows containers on windows hosts). I have read some articles about the pros of worker services, but they

问题 Nowadays in microservice world, i’m seeing alot of design in my workplace that uses kafka messaging when you can achieve similar results using rest api calls between microservices. Technically you can stop using rest api calls altogether and instead use kafka messaging. I really want to know the best practice, pros and cons, when to use api calls between microsevices, when to use kafka messaging. Lets put a real life example: I have an inventory service and a vendor service. Everyday vendor