micro-service | : gem : Spring Cloud demo based on Camden.SR5 | Microservice library

I'm trying to setup a dotnet micro-service backend with a gateway using Ocelote. Doing this as described, Ocelote provides me with multiple swagger definitions (for each micro-service)


Since the API now has multiple definition, each definition has its own defining json file.

How can i generate the API services and Models using openapi-generator-cli in this case. Previously i only had one definition which i generated with the command below, passing it the published json file directly

I've got an edge service which consolidates results from 3 different micro-services.

1. Returns a Flux of customers
2. Returns Mono of profile for customer
3. Returns a Flux of roles for customer

What is the correct way to build a Flux of CustomerProfile objects which will include information about customer, profile and roles?

This should be fairly easy, or I might doing something wrong, but after a while digging into it I couldn't find a solution.

I have a Terraform configuration that contains a Kubernetes Secret resource which data comes from Vault. The resource configuration looks like this:

I'm running into status code 413 Request Entity Too Large. I'm running an Amazon Linux 2 AMI instance on AWS's Elastic Beanstalk, which is running an express server with a post route that uploads files to an S3 Bucket and then both adds some data to a table and produces a kafka message. Everything is working properly with files below 1MB size.

I understand nginx's default max-size value is 1MB and that I must change it.

I tried every answer in this thread Increasing client_max_body_size in Nginx conf on AWS Elastic Beanstalk but despite getting the client_max_body_size 10M; inside the nginx.conf file, and restarting nginx everytime I changed a configuration, using nginx -t to see if anything was wrong with the syntax, resulting in everything being ok, and finally proving via this command that the client_max_body_size 10M; line was in fact there, when it accused of there being a duplicate of it inside the file, all of these configs seemed to be completely ignored by my micro-service whenever I try to post a file greater than 1MB.

i added client_max_body_size 10M; manually to show that, when testing, nginx tells me it's duplicate, proving it was already included in the nginx.conf file

I also tried to put my conf files inside a .platform/conf.d/ structure, which did make the client_max_body_size 10M; go inside the nginx.conf file, but still it made no difference for my request.

I've also tried reload and restarting the nginx service, both to no avail.

I don't have much ideas on where to proceed from here. Any tips?

I'm working on a SpringBootApplication. In this app I have 4 micro-services using Feign to communicate between eachothers. In a Controller I have a piece of code like this below, to catch exceptions and return it to the view, in case something is wrong.

To define a VPC Link into API Gateway we have to declare an NLB in eks (LoadBalancer service) to access the pod in the VPC.

When we define ingress resource, we can group them into one ALB with the annotation alb.ingress.kubernetes.io/group.name

It seems not possible to do the same with multiple service as a network load balancer. Is it possible ? Or just a bad idea to expose multiple micro-service (with different endpoint) on the same NLB with port as discriminant ?

In our organisation, we have a software system, powered by multiple microservices namely :-

• Aggregator MS.
• Customer MS.
• Document MS.

Each of the aforesaid micro-service have a master branch, which has latest codebase.

Now, there are multiple verticals which are actively developing & contributing to aforesaid microservices. Some of the verticals(independent group of developers) are for example :-

• Vertical-A
• Vertical-B
• Vertical-C

There are pre-defined strategies for each vertical (into which they do their development) and some common code as well, in the above microservices.

Also, each vertical have Infrastructure level segregation, which means there are 3 independent cluster-setups for each vertical.

Post their respective deployment, each vertical merges their code to the respective master branches. Now, if another vertical has to do their development, they have to rebase their feature/local branch with master and then proceed.

Now the Problem is :-

Whenever Say Vertical-A introduces some change in any of three microservices, they need to take the signoff from remaining verticals i.e. Vertical-B & Vertical-C. In another sense, we have a huge inter-dependence of one vertical on other verticals.

I shall be thankful to the community here, if you can suggest some ways of de-coupling the code here.

Any pointers or references would be highly appreciated & welcome.

-- Thanks aditya

I have installed cert manager on a k8s cluster:

I am trying to migrate our cassandra tables to use liquibase. Basically the idea is trivial, have a pre-install and pre-upgrade job that will run some liquibase scripts and will manage our database upgrade.

For that purpose I have created a custom docker image that will have the actual liquibase cli and then I can invoke it from the job. For example: