Lemnoria Relay
Be sure your data reaches its destination.
Relay safely stores incoming order, product and stock data first, then delivers it to your system. Nothing is lost even when the target system is down, and you can see where every record is from the dashboard.
Source system
Sends the data
Relay
Waiting
Your system
Ready
The source system sends the data.
Schematic illustration.
How it works
Safe delivery in four steps
The path incoming data takes until it reaches your system.
- 01
Record received
Incoming data is written durably and the sender immediately gets a “received” response. Every record carries a tracking number so it can be followed end to end.
- 02
Transformed and mapped
Data is converted into the format the target system expects. If the mapping for a code such as a category or carrier is missing, the record does not fail; it waits until the mapping is added, then flows on its own.
- 03
Delivered to the target
Each request goes out with an idempotency key, so the same record is never processed twice. If the target does not respond or its credentials break, Relay pauses and the queue stays intact.
- 04
Monitored and managed
In the dashboard you see the status of each record and retry, ignore, or correct and resend as needed. Every intervention is written to the audit log.
Guarantees
What is guaranteed during transfer
No data loss
The “received” response means the data has been written to the database.
No double processing
A repeated request with the same source and key does not create a new record; the key is also sent to the target.
The queue survives a down target
On an authorization error or outage Relay pauses and records wait; they continue on their own once the target recovers.
End-to-end traceability
The tracking number is carried from the incoming request to the record in the target system.
A missing mapping is not an error
A missing mapping puts the record in “waiting”; no retry attempts are used up and no alarm storm follows.
Operator intervention
Retry, ignore, correct and send, add a mapping. Every action is in the audit log.
Operations dashboard
The status of every record in one place
See which record was delivered, which is waiting and which is missing a mapping, and step in right from the dashboard.
| Record | Source | Status | Attempts | Note |
|---|---|---|---|---|
| order-10482 | Warehouse system | Delivered | 1 | Delivered to the target |
| product-5521 | Marketplace | Awaiting mapping | 0 | No mapping for the “electronics” category |
| stock-8830 | Warehouse system | Will retry | 2 | Target returned a temporary error |
| order-10477 | Warehouse system | Failed | 5 | Target rejected the record (422) |
Retry
Puts the record back in the queue once a temporary problem is fixed.
Correct and send
Fixes the payload and resends it with the same tracking number.
Add mapping
Enters the missing mapping; all waiting records are released.
Ignore
Closed with a reason; the reason is mandatory.
Scope
What is ready today
Ready
- ✓Receiving incoming data and delivering it to the target system: the end-to-end flow has been tested with a sample target system.
- ✓Operations dashboard: overview, records, mappings, routes and audit.
- ✓Single-server setup with Docker Compose.
Per project / to be developed
- ○Customer-specific transformer: written per project against your system contract and tested together before go-live.
- ○Outbound delivery (e-commerce and marketplace adapters): in design, not yet coded.
- ○Large-scale architecture (gateway, replica, broker): draft.
