DataLink Nexus

Queue Types

One-to-One one-to-one

Single consumer delivery with visibility key enforcement. Only one message per visibility key can be in-flight at a time. Primary key deduplication, configurable consume TTL, and max message age.

One-to-Many one-to-many

Independent message copies delivered to multiple consumers. Each consumer tracks their own position and must acknowledge before receiving the next message. Primary key deduplication.

Key-Value key-value

State snapshot and lookup store. Items keyed by primary key with optional sort key. Get all items, get by key, or get only updates since your last request. Supports replace-on-duplicate.

Time-Series time-series

Numeric field aggregation into selectable time buckets — from 1 minute up to daily (1440 min). Computes OHLC stats, sum, count, and average per bucket. Clock-aligned boundaries for consistent reporting.

Stream-to-One stream-to-one

Enrichment queue for single consumers. On publish, messages are automatically joined with data from a linked key-value queue via foreign key lookup. Configurable missing lookup policy (reject or defer).

Stream-to-Many stream-to-many

Enrichment queue for multiple consumers. Same key-value lookup enrichment as stream-to-one, but delivers independent copies to each consumer. Configurable missing lookup policy (reject or defer).

Document document

Whole-file document repository. Upload XML/CSV/JSON files kept intact as a single document, list them, and download in any format via the Accept header. Optional retention (TTL) and cross-tenant document subscriptions.

Text Document text-document

Plain-text document repository — the text/plain sibling of Document. Upload text files stored and served verbatim (no format conversion or validation), list them, and download by name. Optional retention (TTL) and cross-tenant text-document subscriptions.

Getting Started

1

Access Your Tenant

Sign in to the Tenant Dashboard. New users are onboarded by email invitation — follow the invite link to set your password and join your tenant.

2

Create Queues

Choose from eight queue types. Configure primary keys, visibility keys, TTLs, overflow policies, and lookup relationships.

3

Create API Clients

Create client credentials with granular permissions. Control which clients can publish, consume, or both.

4

Publish & Consume

Use the REST API or the Client Dashboard to publish messages, consume, acknowledge, and manage your data.

Dashboards

Tenant Dashboard

Create and configure queues of all eight types
Manage API clients and their publish/consume permissions
Set up cross-tenant queue subscriptions
Monitor dead letter queues and replay messages
View real-time activity logs and message charts
Edit queue configurations (TTLs, depth, overflow policy)
Track audit log history for compliance

Client Dashboard

Publish messages to queues (individual, batch, or whole-file upload)
Choose batch semantics: best-effort or all-or-nothing (file uploads are always all-or-nothing)
Consume messages with optional header filtering
Acknowledge and negative-acknowledge messages
Manage key-value items (publish, get by key, get updates)
Query time-series buckets with aggregated statistics
Track in-flight messages awaiting acknowledgement
Supports JSON, CSV, and XML content types

Key Features

Multi-Tenancy

Complete tenant isolation with invitation-based user onboarding. Each tenant has independent queues, clients, and encryption keys in their own database.

JWT Authentication

Three-tier authentication: admin, tenant, and client tokens with refresh token support. Granular publish/consume permissions per client.

Cross-Tenant Subscriptions

Subscribe to queues across tenant boundaries. Tenant owners control which queues allow subscriptions, enabling secure data sharing between tenants.

Dead Letter Queues

Automatic dead-lettering for expired, nacked, and lookup-failed messages. Browse, inspect, replay back to the active queue, or purge.

Field-Level Encryption

Per-tenant encryption with AES-GCM and AES-SIV. SHA-256 hashing enables filtered searches on encrypted data. 30-day key rotation support.

Content Conversion

Publish in JSON, CSV, or XML — individually, in batches, or as a whole-file upload. Consume in any format via Accept headers. Automatic conversion between formats with no extra configuration.

Rate Limiting

Configurable per-endpoint rate limits protect the broker from overload. Separate limits for auth, publish, consume, and admin operations.

Audit Logging

Complete audit trail of all operations. Track publishes, consumes, acks, nacks, configuration changes, and entity lifecycle events.

Data Masking & Tokenization

Protect sensitive data like PANs and SSNs with irreversible masking or deterministic tokenization. Applied before encryption on publish, with full detokenization support for authorized consumers.

Request a dev instance

Get your own DataLink Nexus dev instance on a free 14-day trial. Tell us who you are and we'll set it up for you.