guicedee-service-registry
Named service registry with health-aware resolution for GuicedEE. Register services by simple name, auto-construct URLs from cloud DNS suffix, monitor health status, resolve services via registry:name prefix or bare name in rest-client @Endpoint. Supports aliases, multiple external URLs, Kubernetes internal URLs, and per-service health paths. Use when registering named services, checking service health, resolving service URLs by name, or integrating with rest-client for service-to-service calls.
Best use case
guicedee-service-registry is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Named service registry with health-aware resolution for GuicedEE. Register services by simple name, auto-construct URLs from cloud DNS suffix, monitor health status, resolve services via registry:name prefix or bare name in rest-client @Endpoint. Supports aliases, multiple external URLs, Kubernetes internal URLs, and per-service health paths. Use when registering named services, checking service health, resolving service URLs by name, or integrating with rest-client for service-to-service calls.
Teams using guicedee-service-registry should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/guicedee-service-registry/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How guicedee-service-registry Compares
| Feature / Agent | guicedee-service-registry | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Named service registry with health-aware resolution for GuicedEE. Register services by simple name, auto-construct URLs from cloud DNS suffix, monitor health status, resolve services via registry:name prefix or bare name in rest-client @Endpoint. Supports aliases, multiple external URLs, Kubernetes internal URLs, and per-service health paths. Use when registering named services, checking service health, resolving service URLs by name, or integrating with rest-client for service-to-service calls.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GuicedEE Service Registry
Named service registry with health monitoring — register, discover, and resolve services by simple name.
## Core Concept
The service registry maintains a map of `name → URL + health status`. Services are registered via annotations, auto-constructed from cloud DNS suffix, or provided by SPI plugins. Periodic health checks keep status current. The rest-client module can resolve `registry:service-name` URLs or bare service names at call time.
## Required Flow
1. Add `com.guicedee:service-registry` dependency.
2. Add `requires com.guicedee.service.registry;` to `module-info.java`.
3. Declare services on `package-info.java`:
```java
@ServiceRegistryOptions(healthCheckInterval = 30)
@RegisteredService(name = "jwebmp-website",
aliases = {"jwebmp", "jwebswing"},
externalUrls = {"https://jwebmp.com", "https://jwebswing.com"},
kubernetesUrl = "http://jwebmp-website.default.svc.cluster.local")
@RegisteredService(name = "payment-api", url = "${PAYMENT_URL}", healthPath = "/status")
@RegisteredService(name = "hello-service",
url = "http://hello-service.myns.svc.cluster.local",
healthPath = "/healthz")
package com.myapp;
```
4. Use services by name:
```java
String url = ServiceRegistry.url("jwebmp-website");
String url = ServiceRegistry.url("jwebmp"); // alias resolution
String ext = ServiceRegistry.externalUrl("jwebmp-website"); // → https://jwebmp.com
List<String> exts = ServiceRegistry.externalUrls("jwebmp-website");
String k8s = ServiceRegistry.kubernetesUrl("jwebmp-website");
Optional<String> healthy = ServiceRegistry.healthyUrl("jwebmp-website");
```
## JPMS Module Name
`com.guicedee.service.registry`
## Lifecycle Hooks
| Hook | Sort Order | What It Does |
|---|---|---|
| `ServiceRegistryPreStartup` | `MIN+150` | Scans annotations, constructs URLs, self-registers, runs SPI providers |
| `ServiceRegistryPostStartup` | `MIN+700` | Starts Vert.x periodic health check timer |
## Key Classes
| Class | Package | Role |
|---|---|---|
| `ServiceRegistry` | `com.guicedee.service.registry` | Central static registry — `get()`, `url()`, `externalUrl()`, `externalUrls()`, `kubernetesUrl()`, `healthyUrl()`, `resolve()`, `register()`, `registerAlias()` |
| `ServiceEntry` | `com.guicedee.service.registry` | Record: name, url, externalUrls, kubernetesUrl, healthPath, status, lastChecked, metadata |
| `ServiceStatus` | `com.guicedee.service.registry` | Enum: UP, DOWN, UNKNOWN, DEGRADED |
| `ServiceRegistryOptions` | `com.guicedee.service.registry` | Annotation: healthCheckInterval, healthPath, registerSelf, useHttps, defaultPort |
| `RegisteredService` | `com.guicedee.service.registry` | Annotation: declares a known service (repeatable) — name, url, healthPath, aliases, externalUrls, externalUrl, kubernetesUrl |
| `IServiceRegistryProvider` | `com.guicedee.service.registry` | SPI for external catalogs (Azure API, Consul, static config) |
## URL Resolution Order
1. If `@RegisteredService(url = "...")` is provided → use it (supports `${ENV_VAR}` placeholders)
2. If url is empty, auto-construct from DNS suffix:
- Check `CONTAINER_APP_ENV_DNS_SUFFIX` env var (Azure Container Apps)
- Check `runtime-autoconfigure` extras.dnsSuffix (if on classpath)
- Check `SERVICE_REGISTRY_DNS_SUFFIX` env var (manual fallback)
- URL = `https://{name}.{dnsSuffix}`
3. If no DNS suffix available → warning logged, service skipped
## Aliases & External URLs
- `aliases = {"jwebmp", "jwebswing"}` — all resolve to the same service entry
- `externalUrls = {"https://jwebmp.com", "https://jwebswing.com"}` — public custom domains
- `externalUrl = "https://guicedee.com"` — single external URL shorthand
- `kubernetesUrl = "http://svc.ns.svc.cluster.local"` — K8s internal cluster URL
- `ServiceRegistry.externalUrl("name")` returns first external URL or falls back to internal
- `ServiceRegistry.kubernetesUrl("name")` returns K8s URL or falls back to internal
## Per-Service Health Paths
Each `@RegisteredService` can specify its own `healthPath`:
```java
@RegisteredService(name = "legacy-app", healthPath = "/status")
@RegisteredService(name = "k8s-service", healthPath = "/healthz")
@RegisteredService(name = "standard-service") // uses registry default "/health/ready"
```
`ServiceEntry.healthUrl()` concatenates `url + healthPath` to get the full health check URL.
## Self-Registration
When `registerSelf = true` (default) and `runtime-autoconfigure` is on classpath:
- Uses `RuntimeAutoConfigurePreStartup.current()` to get serviceName, hostname, port
- Registers self with status UP and metadata `{self: "true"}`
- Self entries are skipped during health checks
## Automatic Discovery (preferred — do not hand-roll)
GuicedEE discovers peers **automatically**; do **not** maintain a hand-written peer
list or build a custom `IServiceRegistryProvider` just to enumerate known services.
Three built-in mechanisms cooperate:
1. **Self-registration** (`registerSelf = true` + `runtime-autoconfigure`) — every
service advertises its own identity/host/port at startup. No peer declares another.
2. **DNS-suffix URL construction** — when a name has no explicit URL, the registry
builds `https://{name}.{dnsSuffix}` from the first available of
`CONTAINER_APP_ENV_DNS_SUFFIX` (Azure Container Apps), `runtime-autoconfigure`
`dnsSuffix`, or `SERVICE_REGISTRY_DNS_SUFFIX` (manual fallback).
3. **`service-discovery` module** (`com.guicedee.vertx.servicediscovery`) — a Vert.x
service resolver (Kubernetes / SRV aware) that resolves service names to live
addresses at call time. Add the dependency + `requires
com.guicedee.vertx.servicediscovery`; it self-activates via lifecycle SPIs (no
wiring). This is the "automatic discovery" backbone for clustered/K8s deployments.
```java
// Idiomatic: declare ONLY options; rely on self-registration + discovery for peers.
@ServiceRegistryOptions(healthCheckInterval = 30, registerSelf = true, useHttps = true)
package com.myapp;
```
> **When to still use `@RegisteredService`.** Only for genuinely *external* / third-party
> endpoints that cannot self-register (a legacy API, a public site). Never to list your
> own platform's GuicedEE services — those self-register and are discovered.
> **Local-dev caveat.** With no cloud platform and no DNS suffix, `runtime-autoconfigure`
> cannot resolve a public URL, so the self entry may carry an empty URL and a periodic
> health check can show it `DOWN`. This is expected for plain local runs — real discovery
> happens in the target environment. Set `SERVICE_REGISTRY_DNS_SUFFIX` locally if you want
> name → URL construction, or run the cluster (K8s/compose) where the resolver applies.
## Health Checks
- Periodic HTTP GET to `{url}{healthPath}` using Vert.x WebClient
- 2xx/3xx → UP, 503 → DEGRADED, other → DOWN, connection failure → DOWN
- Configurable interval (default 30s) and timeout (default 5000ms)
- `trustAll = true` by default (for dev clusters)
## Integration with rest-client
The rest-client auto-resolves from service registry (no hard dependency):
```java
// Explicit registry: prefix
@Endpoint(url = "registry:jwebmp-website")
@Named("jwebmp") private RestClient<Void, Response> client;
// Bare service name (auto-detected if registered)
@Endpoint(url = "jwebmp-website")
@Named("jwebmp") private RestClient<Void, Response> client;
// Full URL (passes through unchanged)
@Endpoint(url = "https://api.example.com/v1")
@Named("example") private RestClient<Void, Response> client;
```
## Optional Dependencies
| Module | Maven artifact / module name | What It Adds |
|---|---|---|
| `runtime-autoconfigure` | `com.guicedee:runtime-autoconfigure` (`com.guicedee.runtime.autoconfigure`) | Self-registration + DNS suffix auto-detection across cloud platforms (AWS, Azure, GCP, K8s, Fly.io, Render, …) |
| `service-discovery` | `com.guicedee:service-discovery` (`com.guicedee.vertx.servicediscovery`) | **Automatic** Vert.x service resolution (Kubernetes / SRV aware) via the `IServiceResolverProvider` SPI; self-activates through lifecycle hooks |
## @ServiceRegistryOptions Attributes
| Property | Default | Purpose |
|---|---|---|
| `healthCheckInterval` | `30` | Seconds between checks (0 = disabled) |
| `healthPath` | `"/health/ready"` | Default health endpoint path |
| `registerSelf` | `true` | Auto-register using runtime-autoconfigure |
| `healthCheckTimeout` | `5000` | HTTP timeout in ms |
| `useHttps` | `true` | HTTPS for auto-constructed URLs |
| `defaultPort` | `0` | Port for auto-constructed URLs (0 = omit) |
## @RegisteredService Attributes
| Property | Default | Purpose |
|---|---|---|
| `name` | (required) | Simple logical service name |
| `url` | `""` | Full URL (empty = auto-construct from DNS suffix). Supports `${ENV_VAR}` |
| `healthPath` | `""` | Health path override (empty = use registry default) |
| `aliases` | `{}` | Alternative names that resolve to this service |
| `externalUrls` | `{}` | External/public URLs (custom domains). Supports `${ENV_VAR}` |
| `externalUrl` | `""` | Single external URL shorthand. Supports `${ENV_VAR}` |
| `kubernetesUrl` | `""` | Kubernetes internal cluster URL. Supports `${ENV_VAR}` |
## IServiceRegistryProvider SPI
```java
public class AzureCatalogProvider implements IServiceRegistryProvider<AzureCatalogProvider> {
@Override
public List<ServiceEntry> discover() {
// Call Azure API, return container apps in environment
}
@Override
public String providerId() { return "azure-catalog"; }
}
```
Register in `module-info.java`:
```java
provides IServiceRegistryProvider with AzureCatalogProvider;
```
> **Don't reach for this SPI to list your own services.** It exists to bridge a *real
> external catalog* (Azure Resource Graph, Consul, a CMDB). Implementing one that just
> reads a static/env-driven peer list (e.g. `NE1_REGISTRY_PEERS=name=url;…`) is an
> anti-pattern — it re-invents what self-registration + the `service-discovery` resolver +
> DNS-suffix construction already do automatically. Prefer those (see *Automatic
> Discovery*); use a custom provider only when integrating an authoritative external
> registry.
## Non-Negotiable Constraints
- Module name: `com.guicedee.service.registry`
- `IGuicePreStartup.onStartup()` returns `List<Future<Boolean>>` (Vert.x Future)
- `IGuicePostStartup.postLoad()` returns `List<Uni<Boolean>>` (Mutiny Uni)
- Vert.x WebClient module name is `io.vertx.web.client`
- Vert.x Web module name is `io.vertx.web`
- Sort order must be after `RuntimeAutoConfigurePreStartup` (MIN+50) and after `VertXPreStartup`
- All services stored lowercase/trimmed
- `resolveEnvPlaceholders` is public for cross-package accessRelated Skills
guicedee-websockets
RFC 6455 WebSocket support for GuicedEE using Vert.x 5: call-scoped connections, action-based message routing via IWebSocketMessageReceiver SPI, group management and broadcasting, WebSocketServerOptions, and lifecycle hooks. Use when adding WebSocket messaging, implementing real-time communication, managing WebSocket groups, or creating message receivers.
guicedee-webservices
SOAP web services for GuicedEE using Apache CXF conventions: JAX-WS annotations (@WebService, @WebMethod, @WebParam, @WebResult), code-first and WSDL-first approaches, endpoint publishing, CXF interceptors and logging, MTOM, WS-Security (WSS4J), SOAP 1.1/1.2 bindings, and Guice DI integration. Use when creating SOAP services, publishing JAX-WS endpoints, configuring CXF bindings, or adding WS-Security.
guicedee-web
Bootstrap reactive HTTP/HTTPS servers with Vert.x 5 inside GuicedEE: Router setup, BodyHandler configuration, TLS/HTTPS, SPI extension points (VertxRouterConfigurator, VertxHttpServerOptionsConfigurator, VertxHttpServerConfigurator), per-verticle sub-routers, and environment-driven configuration. Use when setting up the Vert.x web server, configuring HTTP/HTTPS, adding custom routes or middleware, or managing server options.
guicedee-vertx
Build reactive services using Vert.x 5 inside the GuicedEE DI lifecycle: event-bus consumers, publishers, verticle deployment, codecs, throttling, clustering, SPI hooks, and JPMS module setup. Use when adding Vert.x event-bus messaging, deploying verticles, wiring reactive endpoints with Guice injection, configuring Vert.x runtime options, or implementing custom codecs and cluster managers.
guicedee-rest
Build Jakarta REST (JAX-RS) services on Vert.x 5 inside GuicedEE: @Path/@GET/@POST route registration, parameter binding (@PathParam, @QueryParam, @HeaderParam, etc.), Guice-managed resource classes, response handling, content negotiation, and JPMS module setup. Use when creating REST endpoints, configuring Jakarta REST resources, or wiring JAX-RS services with Guice injection.
guicedee-rest-client
Annotation-driven REST client for GuicedEE using Vert.x 5 WebClient: @Endpoint declarations, RestClient<Send, Receive> injection, authentication strategies (Bearer, Basic, API Key, OAuth2, mTLS), path parameters, environment variable overrides, package-level endpoints, service registry integration (bare name or registry: prefix), and RestClientConfigurator SPI. Use when making outbound REST calls, configuring REST client endpoints, or wiring reactive HTTP clients with Guice injection.
guicedee-rabbitmq
Annotation-driven RabbitMQ integration for GuicedEE with Vert.x 5: @RabbitConnectionOptions, @QueueExchange, @QueueDefinition, QueueConsumer/QueuePublisher injection, exchange management, queue options (priority, TTL, prefetch), publisher confirms, environment variable overrides, and verticle-scoped connections. Use when adding RabbitMQ messaging, declaring exchanges and queues, creating consumers and publishers, or configuring AMQP topology.
guicedee-persistence
Reactive JPA persistence with Hibernate Reactive 7, Vert.x 5 SQL clients, and Mutiny sessions inside GuicedEE: DatabaseModule setup, persistence.xml configuration, multi-database support, @EntityManager scoping, and environment variable resolution. Use when adding database persistence, configuring Hibernate Reactive, creating DatabaseModule subclasses, wiring Mutiny.SessionFactory, or managing multiple persistence units.
guicedee-openapi
Automatic OpenAPI 3.1 spec generation and serving for GuicedEE with Vert.x 5: scans Jakarta REST resources at startup, serves /openapi.json and /openapi.yaml endpoints, Swagger annotations support, @OpenAPIDefinition configuration, and companion Swagger UI module. Use when generating API documentation, serving OpenAPI specs, or configuring Swagger annotations on REST resources.
guicedee-metrics
Application metrics for GuicedEE using Vert.x 5 Dropwizard Metrics and MicroProfile Metrics 5.1: @Counted, @Timed, @MetricMethod annotations, Guice AOP interceptors, Prometheus scrape endpoint, Graphite reporting, JMX exposure, @MetricsOptions configuration, environment variable overrides, and Vert.x built-in metrics (event bus, HTTP, pools). Use when adding application metrics, configuring Prometheus endpoints, creating custom counters/timers, or monitoring Vert.x internals.
guicedee-mail-client
Annotation-driven SMTP mail client for GuicedEE with Vert.x 5: @MailConnectionOptions for SMTP server configuration, MailService injection for sending text/HTML/multipart emails with attachments, connection pooling, StartTLS/SSL support, DKIM signing, environment variable overrides, and graceful shutdown. Use when sending emails via SMTP, configuring mail connections, or injecting mail services.
guicedee-kafka
Annotation-driven Kafka integration for GuicedEE with Vert.x 5: @KafkaConnectionOptions, @KafkaTopicDefinition, @KafkaTopicCreate, KafkaTopicConsumer/KafkaTopicPublisher injection, KafkaAdminClient binding, per-topic consumers, manual offset commit, worker thread support, partition assignment and revocation handlers, environment variable overrides, call-scoped message handling, and graceful shutdown. Use when adding Kafka messaging, declaring topic consumers and publishers, creating topics via admin client, or configuring Kafka connections.