README

Thin service registry for KislayPHP. Register instances, track health, and resolve healthy URLs without embedding business logic.

Installation

Via PIE (recommended):

pie install kislayphp/discovery:0.0.7

Add to php.ini:

extension=kislayphp_discovery.so

Role In The Stack

Discovery only does:

• register service instances
• update health/status
• resolve service name to healthy instance URL
• expose thin registry HTTP endpoints when running standalone

Discovery does not do:

• business logic
• request execution
• JWT handling
• trace mutation

Quick Start

Start the registry

<?php

$registry = new Kislay\Discovery\ServiceRegistry();
$registry->listen('0.0.0.0', 9010);
$registry->run();

Register a service

<?php

$registry = new Kislay\Discovery\ServiceRegistry('http://127.0.0.1:9010');
$registry->register('user-service', 'http://127.0.0.1:9008', ['zone' => 'az-1'], 'user-1');

Resolve a service

<?php

$registry = new Kislay\Discovery\ServiceRegistry('http://127.0.0.1:9010');
$url = $registry->resolve('user-service');
var_dump($url);

Runtime Behavior

• resolve() only returns UP and heartbeat-fresh instances.
• stale instances are lazily pruned before local read paths return data.
• weighted selection uses std::mt19937, not rand().
• registration is capped per service to avoid unbounded growth.
• standalone server mode exposes registry-only HTTP endpoints.

Optional Redis Storage

Discovery supports:

• memory backend by default
• redis backend optionally for shared registry state

When Redis is configured:

• writes are mirrored locally and sent to Redis
• reads attempt Redis first
• on Redis failure, Discovery falls back to in-memory state with a warning
• fallback preserves node-local safety, not cluster-wide strong consistency

Environment Variables

Notes

• In-memory mode is still the simplest local default.
• Redis mode gives shared registry storage without adding a client library dependency.
• If Redis is unavailable, fallback is safe but degrades to node-local view.

License