Ask or search…
Learn by example
How to contribute?
Memphis Functions (Beta)
Use cases and best practices
Self-hosted to Cloud Guide
Node.js / TypeScript / NestJS
Change data Capture (CDC)
v1.4.3 - latest/stable
V1.0.0 - GA
v0.4.5 - beta
v0.4.4 - beta
v0.4.3 - beta
v0.4.2 - beta
v0.4.1 - beta
v0.4.0 - beta
v0.3.6 - beta
v0.3.5 - beta
v0.3.0 - beta
v0.2.2 - beta
v0.2.1 - beta
v0.2.0 - beta
v0.1.0 - beta
Release date: Jan 3, 2024
: Redis (a key-value database) and Memphis sink connectors are now available.
: key-based message routing
Enhanced control for cloud users over the garbage collection of disconnected clients.
Consumer client garbage collection will preserve offset management, even if all consumers are disconnected.
Role-Based Access Control (RBAC)
implemented for client-type users.
now includes features to run benchmarks.
The user interface will display notifications for clients that require SDK version updates.
A dark mode feature has been added for a better UI experience.
Memphis Functions has entered its Beta phase.
Updates to SDK versions: Node.js SDK has been updated to version 1.3.0, Go SDK to 1.3.0, Python SDK to 1.3.0, and .Net SDK to 0.7.0.
Resolved an issue where creating a schema from the SDK did not generate a new version when the schema already existed.
Fixed a bug where resending unacknowledged messages from the UI resulted in sending the message twice to Node.js-based clients.
Corrected a problem where defining a station with more than one partition as a dead-letter queue for another station was previously not feasible.
Clients using older versions may encounter difficulties when attempting to connect with a user account that has restricted access to stations (due to Role-Based Access Control).
Authentication using connection tokens for the broker is currently non-functional.
The Memphis GUI becomes unresponsive when storage capacity hits 100%, and remains so until the storage is reduced by at least 10%.
Establishing a connection with the broker is slower when connecting via localhost (using port forwarding).
The Slack integration occasionally hits the API rate limit set by Slack, resulting in the loss of some notifications.