explaingit

nepxion/discovery

5,767JavaAudience · developerComplexity · 5/5Setup · hard

TLDR

A Java framework on top of Spring Cloud that adds traffic splitting, blue-green deployments, rate limiting, and circuit breaking to microservice systems, letting teams release new versions to a fraction of users without restarting servers.

Mindmap

mindmap
  root((Nepxion Discovery))
    What it does
      Traffic splitting
      Blue-green deployment
      Zero-downtime releases
    Tech Stack
      Java
      Spring Cloud
      Spring Boot
    Features
      Rate limiting
      Circuit breaking
      Request tracing
      Multi-region failover
    Use Cases
      Gradual rollout
      Traffic rollback
      Service protection
    Audience
      Java engineers
      DevOps teams
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Gradually roll out a new service version to 10% of live traffic to test it in production before a full release.

USE CASE 2

Instantly route all traffic back to the stable version of a service if the new version shows errors, with no restarts.

USE CASE 3

Add rate limiting to a Spring Cloud service to cap how many requests per second it handles during peak load.

USE CASE 4

Enable distributed request tracing across a microservice mesh to see which services handled each incoming request.

Tech stack

JavaSpring CloudSpring Boot

Getting it running

Difficulty · hard Time to first run · 1day+

Requires an existing Spring Cloud microservice setup, README is in Chinese, newer Spring Cloud versions require the paid Polaris tier.

In plain English

Nepxion Discovery is a Java framework built on top of Spring Cloud, aimed at companies that run many small backend services talking to each other (a setup often called microservices). It adds a layer of traffic control on top of what Spring Cloud already provides, letting teams control which version of a service handles which requests, without taking anything offline or restarting servers. The core use case is called blue-green or gray deployment. When a company wants to release a new version of a service, they do not just swap the old one out. Instead, Discovery lets them send a small fraction of real traffic to the new version first, check that it behaves correctly, and then gradually move more traffic over. If something goes wrong, they can send all traffic back to the old version immediately. This is safer than a full cutover and is how large engineering teams release software with minimal risk to real users. Beyond traffic splitting, the framework also handles rate limiting (capping how many requests per second a service can receive), circuit breaking (automatically stopping calls to a service that is failing so the failure does not spread), and request tracing (logging exactly which services handled a request as it passed through the system). There are also failover and multi-region features for teams that run their infrastructure across multiple data centers or cloud regions. The README is written almost entirely in Chinese and is aimed at Java engineers already familiar with Spring Cloud. A companion platform and desktop UI are also mentioned, and there is a commercial version called Polaris with additional features for enterprise buyers. The open-source version covers earlier Spring Cloud releases, newer Spring Cloud versions require the paid tier. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
I am running a Spring Cloud microservice app and want to do a gray deployment. Walk me through configuring Nepxion Discovery to send 10% of traffic to the new version and 90% to the old.
Prompt 2
Show me how to set up circuit breaking with Nepxion Discovery so that if a downstream service fails too often, calls to it stop automatically and a fallback is returned.
Prompt 3
How do I add request tracing to a Nepxion Discovery setup so I can see the full path of a request through multiple Spring Cloud services?
Prompt 4
What is the difference between the open-source Nepxion Discovery and the commercial Polaris version, and which Spring Cloud versions does each support?
Open on GitHub → Explain another repo

← nepxion on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.