// the take
A lightweight config center and service registry for Java services, built by the same author as xxl-job. It gives you dynamic config push, a web admin UI, and basic service registration/discovery backed by nothing more than a shared MySQL database. Fits small-to-mid Spring shops that want config management and service discovery without standing up ZooKeeper, etcd, or Consul.
No external dependency beyond MySQL — one JDBC connection and you're running, which is a real reduction in ops surface compared to ZK/etcd-based alternatives. Clients keep a local snapshot file and fall back to it if the server is unreachable, so a config center outage doesn't take dependent services down with it. Config and registry data both support namespacing, so you get real environment isolation (dev/staging/prod) without separate clusters. The OpenAPI REST layer means non-Java clients aren't locked out, even though the polished SDK experience (annotations, listeners) is Java-only.
It's GPLv3, which is a real blocker for teams shipping proprietary software that links against the client library — worth checking with legal before adopting, not just a housekeeping footnote. Using a plain relational DB as the coordination backend means no real consensus protocol: 'real-time push' is a broadcast-plus-periodic-reconciliation scheme, not a watch guarantee like ZK/etcd give you, so under network partitions you're relying on the local snapshot fallback rather than strong consistency. As a registry it's a standalone system with its own client protocol — it doesn't integrate with Kubernetes service discovery or existing Consul/Nacos infra, so adopting it means running a second, parallel registry. Activity and community are thin (696 stars, effectively single-maintainer, documentation almost entirely in Chinese), so expect to read the source directly when something breaks rather than finding help on Stack Overflow.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →