A message broker for developers made out of devs’ struggles to develop around message brokers.
Enables devs to achieve all other message brokers’ benefits in a fraction of the time.
Focusing on automatic optimization, schema management, inline processing, and troubleshooting abilities. All under the same hood. Utilizing NATS core.
Messaging Platform Screenshots
Why a Golang based Message Broker
Working with data streaming is HARD.
As a developer, you need to build a dedicated pipeline per data source,
change the schema, individual analysis, enrich the data with other sources, constantly crashes, adapt to different rate limits, change APIs, and scale for better performance.
It takes time and resources that you don’t have.
A message broker is an answer. In short – It’s an event store.
Message broker acts as the middleman and supports streaming architecture,
but then you encounter Apache Kafka and its documentation and run back to the monolith and batch jobs.
Give memphis{dev} a spin before.
Message Broker Use-cases
- Async task management
- Real-time streaming pipelines
- Data ingestion
- Cloud Messaging
- Services (microservices, service mesh)
- Event/Data Streaming (observability, analytics, ML/AI)
- Queuing
- N:N communication patterns
Golang based Features
v0.3.0
- Fully optimized message broker in under 3 minutes
- Easy-to-use UI, CLI, and SDKs
- Data-level observability
- Dead-Letter Queue with automatic message retransmit
- SDKs: Node.JS, Go, Python, Typescript, NestJS
- Runs on your Docker or Kubernetes
- Community driven
Roadmap
- Embedded schema store and transformation
- Inline processing
- Connectors and analysis functions
There is no ads to display, Please add some