A service discovery infrastructure for Vert.x microservices, enabling registration and discovery of various service types.
Vert.x Service Discovery is a service discovery infrastructure designed for Vert.x microservice applications. It enables dynamic registration and discovery of services such as REST endpoints, event bus message sources, and service proxies, solving the problem of service location and connectivity in distributed systems. The framework is extensible, allowing integration with external platforms like Kubernetes, Docker, and Consul through bridges.
Java developers building reactive microservices with Vert.x who need dynamic service discovery and integration with container orchestration platforms or service registries.
Developers choose Vert.x Service Discovery for its seamless integration with the Vert.x ecosystem, extensibility via bridges to popular platforms, and support for multiple service types and storage backends, enabling flexible and scalable microservice architectures.
Some tools one can use for doing microservices with Vert.x
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers pluggable bridges to import services from Kubernetes, Docker, and Consul, enabling seamless integration with external platforms, as highlighted in the README's support for multiple discovery bridges.
Supports built-in types like REST endpoints, event bus message sources, and service proxies, and allows defining custom service types for tailored needs, as mentioned in the documentation.
Provides alternative backends such as Redis via the vertx-discovery-backend-redis module, offering flexibility beyond the default distributed map for storing service records.
Designed specifically for Vert.x applications, ensuring compatibility with the reactive, non-blocking nature of the ecosystem, which is central to its philosophy.
The vertx-discovery-bridge-docker is labeled as experimental in the README, indicating instability and unsuitability for production environments without caution.
Heavily reliant on the Vert.x framework, making it ineffective for projects outside the Vert.x or JVM-based microservices landscape, limiting its broader adoption.
Focuses primarily on registration and discovery, lacking advanced features like automatic health checks or load balancing that are common in other service discovery tools, as not detailed in the README.