fahara02 / udb-laravel
Laravel SDK for UDB (Universal Data Broker) — gRPC client, ServiceProvider, Facade, request-context middleware, and tenant-aware request injection.
Requires
- php: ^8.1
- ext-grpc: *
- google/protobuf: ^4.33.6
- grpc/grpc: ^1.57
- illuminate/contracts: ^10.0|^11.0|^12.0
- illuminate/support: ^10.0|^11.0|^12.0
Requires (Dev)
- friendsofphp/php-cs-fixer: ^3.50
- orchestra/testbench: ^8.0|^9.0|^10.0
- pestphp/pest: ^2.0|^3.0
- pestphp/pest-plugin-laravel: ^2.0|^3.0
- phpstan/phpstan: ^1.10
- symfony/event-dispatcher: ^6.0|^7.0
- symfony/http-kernel: ^6.0|^7.0
Suggests
- symfony/event-dispatcher: Required by the Symfony UdbContextSubscriber (kernel.event_subscriber).
- symfony/http-kernel: To use the Symfony adapter (Fahara02\UdbLaravel\Symfony\UdbContextSubscriber) for request-scoped UDB context.
README
UDB :: Universal Data Broker
gRPC data plane | native control plane | tenant/project scope guard
crate v0.4.21 | protocol v1.0.0
Laravel client for UDB, a service that lets your app read and write data through one broker instead of connecting directly to every database or storage backend.
Install this package when a Laravel app needs to call a running UDB broker. It gives you a Laravel ServiceProvider, a Udb facade, generated PHP protobuf classes, request middleware, and clear exceptions for gRPC errors.
What is UDB?
UDB stands for Universal Data Broker. Think of it as a data API that sits between your Laravel app and the systems where the data actually lives.
A Laravel app sends a request such as "select patients", "upsert this invoice", or "delete this object". UDB decides where that data lives, applies the broker rules, talks to the right backend, and returns a typed response.
That means the Laravel app does not need to know whether the data is in Postgres, MySQL, SQLite, MongoDB, S3, Redis, Qdrant, or another supported backend. The app only needs the UDB endpoint and the request it wants to send.
What This Package Does
This package makes UDB feel natural inside Laravel:
composer require fahara02/udb-laravel:^0.4.21- set
UDB_ENDPOINTin.env - call
Udb::select(),Udb::upsert(), orUdb::delete() - use typed generated PHP classes for requests and responses
- let middleware attach tenant, user, and correlation context automatically
- catch Laravel-friendly exceptions instead of handling raw gRPC status arrays everywhere
Requirements
- PHP 8.1+
grpcPECL extension —pecl install grpcthen addextension=grpc.sotophp.ini. The generated stubs extend\Grpc\BaseStub; there is no fallback transport.- Laravel 10, 11, or 12 (Illuminate Container + HTTP + Routing)
- A running UDB broker reachable from the app
Installation
composer require fahara02/udb-laravel:^0.4.21
The service provider is auto-discovered by Laravel. The Udb facade is registered automatically. By default, the package also adds middleware to the web and api route groups so each request can carry tenant and user context into UDB.
The package also installs a version-matched CLI launcher at vendor/bin/udb.
Use it from your Laravel project when you need UDB's shared annotation protos:
vendor/bin/udb proto export --fmt
After that, your app-owned .proto files can import:
import "udb/core/common/v1/db.proto";
Run vendor/bin/udb proto fmt after export or schema edits to keep long UDB
field annotations on one line for easier review.
Publish the config file when you need to override defaults:
php artisan vendor:publish --tag=udb-config
This drops a documented config/udb.php into your app.
Configuration
For local development, the only required value is usually:
UDB_ENDPOINT=127.0.0.1:50051
For production, you will normally set TLS, service identity, project, and timeout values too:
UDB_ENDPOINT=udb.prod.svc.cluster.local:50051 # TLS UDB_TLS_ENABLED=true UDB_TLS_ROOT_CERTS=/etc/ssl/certs/udb-ca.pem UDB_TLS_TARGET=udb.prod.svc.cluster.local # Static metadata (per-request values come from middleware) UDB_SERVICE_IDENTITY=acme.api UDB_PROJECT_ID=acme UDB_DEFAULT_PURPOSE=web.request UDB_DEFAULT_SCOPES=udb:read,udb:write UDB_CLIENT_CATALOG_VERSION=1.0.0 # Timeouts / channel tuning UDB_DEADLINE_MS=30000 UDB_GRPC_KEEPALIVE_MS=30000 UDB_GRPC_MAX_RECV_BYTES=16777216 # Middleware UDB_MIDDLEWARE_AUTO=true
The full reference lives in config/udb.php.
UDB_ENDPOINT accepts either a host:port value or a Unix-domain-socket
target (unix:///var/run/udb.sock) for a co-located broker sidecar — see
Performance below.
Performance
PHP-FPM is shared-nothing: it tears down the worker after every request, so a normal PHP UDB client opens a new gRPC channel per request and re-pays the TCP + TLS + HTTP/2 handshake every time (grpc#15426). That re-handshake is the dominant PHP latency against a gRPC broker.
The fix is to hold a warm channel in a persistent-worker runtime (OpenSwoole / RoadRunner / FrankenPHP) that builds the client once and reuses it across requests, and/or to run a local UDB sidecar reached over a Unix domain socket. See:
- Guide:
docs/php-perf.md— why PHP-FPM can't pool a channel, per-runtime setup recipes, keepalive args, and the local sidecar / UDS pattern (incl. the required broker-side UDS bind, a maintainer follow-up). - Runnable example:
examples/persistent-worker/— a worker that constructs the client once and serves requests on the warm channel (OpenSwoole + RoadRunner + a plain-CLI fallback).
Worker keepalive env (set these for a persistent-worker deployment so the warm channel isn't dropped to IDLE and re-handshaked):
UDB_GRPC_KEEPALIVE_MS=30000 UDB_GRPC_KEEPALIVE_TIMEOUT_MS=10000 # co-located sidecar over a Unix domain socket (needs the broker to bind it): UDB_ENDPOINT=unix:///var/run/udb.sock
Usage
Read Data
use Udb\Entity\V1\SelectRequest; use Fahara02\UdbLaravel\Facades\Udb; $req = (new SelectRequest()) ->setMessageType('acme.healthcare.v1.Patient') ->setLimit(50); $records = Udb::select($req); foreach ($records->getRecords() as $record) { // $record is a typed protobuf object. }
If the call happens during an HTTP request, the middleware will try to attach the current tenant, user, and correlation ID automatically.
Write Data
use Udb\Entity\V1\UpsertRequest; use Fahara02\UdbLaravel\Facades\Udb; $response = Udb::upsert($upsertRequest);
upsert() returns a MutationResponse.
Delete Data
use Udb\Entity\V1\DeleteRequest; use Fahara02\UdbLaravel\Facades\Udb; $response = Udb::delete($deleteRequest);
delete() also returns a MutationResponse.
Idempotency Replay And Read-Your-Writes
A keyed replay-safe mutation the broker deduplicated reports was_duplicate;
the write receipt on the response fences a follow-up read (full contract:
docs/native-services.md).
use Fahara02\UdbLaravel\UdbMetadata; use Fahara02\UdbLaravel\WriteReceipt; use function Fahara02\UdbLaravel\wasReplay; $response = Udb::upsert($upsertRequest); // request carries an idempotency_key if (wasReplay($response)) { // durable-idempotency replay — no new side effect occurred } // Read-your-writes: fence the next read on the write's receipt. $receipt = WriteReceipt::fromJson($response->getWriteReceiptJson()); $meta = UdbMetadata::fromContext(/* ... */)->afterWrite($receipt);
Retry contract: a replay-safe mutation is retried on transient errors only when the request carries a non-empty idempotency key — keyless mutations fail closed rather than risk a double apply.
Queue Jobs And Scheduled Commands
Jobs, commands, and schedulers do not have an HTTP request, so pass metadata explicitly:
use Fahara02\UdbLaravel\UdbMetadata; $meta = UdbMetadata::fromContext( tenantId: 'acme', userId: 'system', correlationId: 'nightly-billing-' . now()->timestamp, purpose: 'scheduled.billing', scopes: ['udb:read', 'udb:billing'], ); $response = Udb::upsert($req, $meta);
Storage (upload & download)
The framework-agnostic UdbProject exposes a storage() facade over the
generated StorageService. Build it with createUdb() (or
UdbProject::connect()), then use the convenience wrappers:
use function Fahara02\UdbLaravel\createUdb; $udb = createUdb([ 'target' => '127.0.0.1:50051', 'tenantId' => 't_acme', 'projectId' => 'default', 'purpose' => 'web.request', 'scopes' => ['udb:read', 'udb:write'], ]); $storage = $udb->storage(); // One-call upload: RegisterUpload -> presigned PUT -> FinalizeUpload. $file = $storage->uploadFile('report.pdf', $bytes, [ 'contentType' => 'application/pdf', 'fileType' => 'report', 'referenceType' => 'invoice', 'referenceId' => 'inv_42', ]); $fileId = $file->getFileId();
Download — happy path (presigned URL). downloadFile() emits exactly one
GetDownloadUrl RPC and returns the typed GetDownloadUrlResponse; the bytes
never transit the broker. Hand the URL to the client / browser:
$dl = $storage->downloadFile($fileId, ['expiresInMinutes' => 15]); $url = $dl->getDownloadUrl(); // `getDownloadUrl($fileId, $expiresInMinutes)` is the un-aliased equivalent.
Download — streaming fallback (new in 0.3.6). When the client cannot reach
the object store over HTTP (no egress, corporate proxy), pull the raw bytes
through the broker with the server-streaming DownloadFile RPC.
downloadFileBytes() opens one server-stream and reassembles each
DownloadFileChunk.data run in order:
// BLOCKING: PHP ext-grpc has no async API, so this returns only after the // final chunk lands (or the deadline trips) and buffers the body in memory. // Prefer the presigned URL above for large objects. $bytes = $storage->downloadFileBytes($fileId); // server default chunk size $bytes = $storage->downloadFileBytes($fileId, 1 << 20); // 1 MiB advisory chunk hint
For RPCs without a wrapper, reach the generated stub via $storage->client().
A runnable end-to-end upload-then-download script lives at
examples/storage-download.php.
Raw gRPC Stub
For broker RPCs that do not have a convenience method yet, use the generated gRPC stub:
$stub = Udb::stub(); $call = $stub->BeginTx($request, Udb::context()->toGrpcMetadata()); [$response, $status] = $call->wait();
Platform Services (Vault, Metering, Scheduler, …)
Vault, Metering, Scheduler, Search, Webhook, Workflow, Lock, LiveQuery, Config,
Backup, and Embedding have no convenience wrappers yet — reach their
buf-generated stubs through the generated client's per-service accessors
(VaultServiceStub(), MeteringServiceStub(), …), which share one channel,
metadata, and TLS configuration:
use Fahara02\UdbLaravel\Generated\GeneratedClient; use Udb\Core\Vault\Services\V1\EncryptRequest; $gen = new GeneratedClient(config('udb')); $stub = $gen->VaultServiceStub(); [$response, $status] = $stub->Encrypt( (new EncryptRequest())->setTenantId($tenant)->setKeyName('docs')->setPlaintext('secret'), Udb::context()->toGrpcMetadata(), )->wait();
The per-RPC retry class and idempotency contract are listed in docs/generated/udb-native-contract.json.
Error handling
use Fahara02\UdbLaravel\Exceptions\UdbRpcException; use Fahara02\UdbLaravel\Exceptions\UdbConfigurationException; use Fahara02\UdbLaravel\Exceptions\UdbException; try { Udb::select($req); } catch (UdbRpcException $e) { // UDB returned a gRPC error. $e->status holds the \Grpc\STATUS_* code. if ($e->status === \Grpc\STATUS_NOT_FOUND) { /* ... */ } } catch (UdbConfigurationException $e) { // Missing endpoint, invalid TLS config, or similar app setup problem. } catch (UdbException $e) { // Base exception for this package. }
Per-request context
The shipped UdbContextMiddleware resolves three values from each incoming HTTP request and binds them to the singleton client so subsequent RPC calls inherit them:
| Value | Default resolver | Header fallback |
|---|---|---|
tenant_id |
$request->user()->tenant_id |
X-Tenant-Id |
user_id |
$request->user()->getAuthIdentifier() |
X-User-Id |
correlation_id |
X-Correlation-Id header |
freshly generated v4 UUID |
Override the resolvers by binding the same container keys in your AppServiceProvider:
$this->app->bind('udb.tenant_resolver', function () { return function (Request $request): ?string { return $request->attributes->get('resolved_tenant_id'); }; });
Testing
The SDK ships with Pest tests + an Orchestra Testbench base class. For your own app's tests, swap the UdbClient binding for a fake:
use Fahara02\UdbLaravel\UdbClient; $this->app->instance(UdbClient::class, $fakeClient = Mockery::mock(UdbClient::class)); $fakeClient->shouldReceive('select')->andReturn(new \Udb\Entity\V1\RecordSet());
Run the SDK's own tests:
composer install composer test # vendor/bin/pest composer analyse # vendor/bin/phpstan
Versioning & compatibility
This SDK follows the UDB wire-protocol version — see UDB_PROTOCOL_VERSION in the parent sdk/ directory. Major SDK versions track major broker versions; minor SDK versions add convenience methods and Laravel-idiomatic helpers.
The current wire protocol is 1.0.0.
License
MIT © fahara02