NATS
Migrate NATS clients to Memphis
Last updated
All rights reserved to Memphis.dev 2023
Migrate NATS clients to Memphis
Last updated
Have you already tried Memphis.dev Cloud?
The motivation behind adding compatibility with NATS API is to
Enable Memphis users to enjoy the broad reach and integrations of the NATS ecosystem.
Enable a lift & shift type of migration from NATS to Memphis.
NATS SDKs version - Compatibility with NATS Jetstream 2.9 and above.
The following Memphis features will not be supported when using NATS SDK:
Producers/Consumers' observability
Schemaverse
Dead-letter station - resend unacked messages
All of NATS core features will be supported when communicating with Memphis, but without performing the below procedure, the Memphis platform will not be able to control and display the created objects, and therefore it is not recommended.
Memphis operates at the stream level. For a NATS subject
to be visible and managed by Memphis, it must first be wrapped by a stream
.
Follow the below instructions based on your Memphis deployment type:
Messages' producers' names will be displayed as "Unknown".
stream
names in NATS are case sensitive, while in Memphis, they are lower-cased, so please consider using only lower-cased names.
In case a station has been created using Memphis GUI/SDK, and you want to produce messages to the same created station, you will have to send the messages into a subject called <stream_name>$<partition_number(starts from 1)>.final
.
In case your station name contains a '.
' sign replace it with '#
' sign in the subject name level.
Using Memphis NATS API compatibility to integrate Memphis with Argo