Search…
Overview

What is Memphis{dev}?

Memphis{dev} is the only low-code real-time data processing platform that provides a full ecosystem for in-app streaming use cases using memphis distributed message broker with a paradigm of produce-consume that supports modern in-app streaming pipelines and async communication by removing frictions of management, cost, resources, language barriers, and time for data-oriented developers and data engineers, unlike other message brokers and queues that requires a great amount of code, optimizations, adjustments, and mainly time.
​memphis.dev started as a fork of the nats.io project (since 2011), written in GoLang, and creating its own stream on top. Instead of topics and queues, Memphis uses stations, which will become an entity with embedded logic in the future.
Memphis focuses on four pillars
  1. 1.
    Performance - Enhancing cache usage
  2. 2.
    Resiliency - Never lose a message and 99.99995% uptime
  3. 3.
    Observability - Out-of-the-box observability that makes sense and reduces troubleshooting time
  4. 4.
    Developer Experience - Modularity, inline processing, schema management, gitops ability

What struggles does Memphis solve?

  1. 1.
    Too many data sources become too complicated to handle.
  2. 2.
    Different and complex schemas get in the way.
  3. 3.
    It's difficult to transform schema and analyze streamed data per source.
  4. 4.
    Currently, stream processing requires stitching multiple applications together like Apache Kafka, Flink, and NiFi. Real-time becomes near-real-time, or far-real-time.
  5. 5.
    Loss of messages due to lack of retransmits, crashes, and monitoring.
  6. 6.
    The event's journey is challenging to debug and troubleshoot.
  7. 7.
    Kafka, RabbitMQ, NATS, and other MQs are HARD to deploy, manage, secure, update, onboard, and tune.
  8. 8.
    Turning batch processes into real-time can be complicated and time-consuming.

Features

Current

  • Fully optimized message broker in under 3 minutes
  • Easy-to-use UI, CLI, and SDKs
  • Data-level observability
  • Runs on your Docker or Kubernetes
  • Message Journey
  • SDKs: Python, Go, Node.js, Typescript, Nest.JS
Coming
  • Embedded schema management using Avro, and Protobuf
  • Ready-to-use connectors and analysis functions
  • More SDKs
  • Inline processing
A full roadmap can be found here https://memphis.dev/roadmap​

The team

We run as one, from marketing to operations to product to development, growing fast and constantly evolving, learning, and doing our best to enjoy the ride.
We highly encourage learning, writing, meetups, contributions to other OSS projects, and community activities.
Our culture is to lead every team member individually to achieve great personal development while maintaining a healthy work-life balance.
As an open-source first company, we consider our precious contributors an essential part of our team, and we do our best to cherish every contributor.

Vision

Our mission is to build the best-in-class dev-first, open-source event-processing platform that will enable millions of developers to better engage with data and build greater data-driven applications and streaming pipelines in friction of time and complexity.

Backed by

Memphis has secured a $5.5M seed round led and supported by the world's best VCs, angels, and advisors -
Boldstart
Angular Ventures
Guy Podjarny (Snyk)
Jim Rose (CircleCI)
David Mytton (Console.dev)
Adam Frankl, Marketing Advisor (JFrog, Neo4j, Sourcegraph)
Martin Brodbeck, Tech Advisor (Priceline, Shutterstock)

Open-Source

Memphis is an open-source first product and company. Memphis will always be open-source and community-driven as we consider the community as the source of power behind building truly disruptive technology.

Locations

Delaware, US
Tel-Aviv, Israel
Scotland, UK
Copy link
Edit on GitHub
Outline
What is Memphis{dev}?
What struggles does Memphis solve?
Features
The team
Vision
Backed by
Open-Source
Locations