The Wayback Machine - https://web.archive.org/web/20201027201711/https://github.com/topics/service-discovery
Skip to content
#

service-discovery

Here are 486 public repositories matching this topic...

DHBin
DHBin commented Mar 31, 2020

Issue Description

Type: bug report

Describe what happened

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance/beat after all servers([minion-register:8848]) tried: failed to req API:minion-register:8848/nacos/v1/ns/instance/beat. code:400 msg: java.lang.IllegalArgumentException: dom name can only have these characters: 0-9a-zA-Z-._:, current: DEFAULT_GROU
miekg
miekg commented Oct 20, 2020

What would you like to be added:
Add a new plugin that minimizes responses as describe (e.g.) in the BIND manual

minimal-responses

 minimal-responses yes | no ;
 minimal-responses yes ;

If yes the server will only add records to the authority and additional data sections when they are required e.g. delegations, negative responses. This may improve the performance of the server. T
express-gateway
XVincentX
XVincentX commented Jan 2, 2018

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

TimHess
TimHess commented Oct 7, 2020

Due to the changes in connectors to separate out Cloud Foundry functionality, some Steeltoe users are struggling with service bindings in cloud hosted scenarios because they don't realize they need another package reference.

In order to improve this experience, (at a minimum for Eureka on Cloud Foundry), write error logs if service bindings aren't detected but are effectively required.

  • Use `Pl

ScaleCube Services is a high throughput, low latency reactive microservices library built to scale. it features: API-Gateways, service-discovery, service-load-balancing, the architecture supports plug-and-play service communication modules and features. built to provide performance and low-latency real-time stream-processing. its open and designed to accommodate changes. (no sidecar in a form of broker or any kind)

  • Updated Sep 21, 2020
  • Java

Demo for Spring Boot 2 and Spring Cloud microservices with distributed configuration (Spring Cloud Config), service discovery (Eureka), API gateway (Spring Cloud Gateway, Zuul), Swagger2 API documentation, logs correlation using Spring Cloud Sleuth and many more

  • Updated Aug 11, 2020
  • Java

Improve this page

Add a description, image, and links to the service-discovery topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the service-discovery topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.