What is Memphis?
Memphis is a next-generation message broker. A simple, robust, and durable cloud-native message broker wrapped with an entire ecosystem that enables fast and reliable development of next-generation event-driven use cases.
Memphis is a tool in the Message Queue category of a tech stack.
Memphis is an open source tool with 2.4K GitHub stars and 152 GitHub forks. Here’s a link to Memphis's open source repository on GitHub
Who uses Memphis?
7 developers on StackShare have stated that they use Memphis.
Python, Node.js, Docker, Java, and TypeScript are some of the popular tools that integrate with Memphis. Here's a list of all 11 tools that integrate with Memphis.
Pros of Memphis
Message broker + Streaming system
- 1-command production deployment
- SDKs: Node.js, TypeScript, NestJS, Python, Go, .NET, Kotlin
- Slack notifications
- Schema Management
Memphis Alternatives & Comparisons
What are some alternatives to Memphis?
See all alternatives
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.
Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.
No related comparisons found