How does N2O compare to Phoenix for real-time apps?

N2O is a lightweight protocol library focused on message handling over WebSocket, MQTT, and TCP, while Phoenix is a full-stack web framework with built-in channels; choose N2O for embeddable, minimal protocol needs, and Phoenix for comprehensive web applications with broader tooling.

How to set up a WebSocket chat with N2O?

Clone the sample repository, run it with rebar3, and access the chat app at localhost:8001; N2O handles the backend protocol loop, and you can extend it with frontend JavaScript from the included libraries like n2o.js.

Does N2O support MQTT 5.0?

The README doesn't specify MQTT versions; it integrates with EMQ for MQTT handling, so support likely depends on the EMQ version used. Check the EMQ documentation or N2O samples for specifics.

What pub-sub backends does N2O work with?

N2O supports GPROC, SYN, and PG2 for pub-sub messaging, providing flexibility in message distribution and allowing integration with existing Erlang/Elixir infrastructure.

Is N2O good for IoT projects?

Yes, with built-in MQTT and TCP protocol support, N2O is well-suited for IoT platforms, as demonstrated in the MQTT chat sample, though it requires Erlang/Elixir expertise for implementation.

How to handle authentication in N2O?

Authentication can be implemented using N2O's session management with ETS storage and encryption services like n2o_secret for AES/GCM-256, but it requires custom setup as no out-of-the-box solution is provided.

Open-Awesome

n2o

NOASSERTIONErlang7.11.1

Embeddable message protocol loop library for WebSocket, HTTP, MQTT, and TCP servers with unified API.

Visit Website GitHub

1.3k stars167 forks0 contributors

What is n2o?

N2O is an embeddable message protocol loop library that provides a unified foundation for building distributed applications over WebSocket, HTTP, MQTT, and TCP. It handles core concerns like process management, virtual node rings, sessions, and frame encoding, enabling high‑performance protocol relay with minimal code.

Target Audience

Erlang/Elixir developers building real‑time, distributed systems such as chat applications, IoT platforms, or enterprise backends that require WebSocket, MQTT, or TCP communication.

Value Proposition

Developers choose N2O for its lightweight, embeddable design, extensive protocol support, and unified API that simplifies integrating multiple messaging and caching services while maintaining high performance and clarity in distributed architectures.

Overview

⭕ N2O: Distributed WebSocket Application Server ISO 20922

Use Cases

Best For

Building real‑time chat applications with WebSocket or MQTT backends
Creating IoT platforms that require MQTT and TCP protocol handling
Developing enterprise systems with BPMN 2.0 business process automation
Implementing distributed microservices with unified message queuing and caching
Embedding a lightweight protocol server into existing Erlang/Elixir applications
Setting up high‑performance API gateways with WebSocket and REST support

Not Ideal For

Projects built with non-Erlang/Elixir stacks
Teams needing out-of-the-box UI components or full-stack frameworks
Simple REST APIs without real-time WebSocket or MQTT requirements
Environments prioritizing extensive third-party integrations and a large community ecosystem

Pros & Cons

Pros

Minimal Codebase

With only 700 lines of Erlang and 500 lines of JavaScript, N2O provides a lightweight foundation for protocol handling, reducing bloat and maintenance overhead.

Extensible Protocol Support

Includes optional protocols like FTP for file transfer and BPE for BPMN 2.0 integration, allowing customization for diverse real-time and enterprise use cases.

Unified Service API

Offers consistent interfaces for formatters (BERT, JSON), session management, and encryption, with support for multiple pub-sub backends like GPROC and SYN, simplifying integration.

Multi-Host Compatibility

Runs on various Erlang/Elixir servers including COWBOY, BANDIT, and EMQ, making it adaptable to different deployment environments without vendor lock-in.

Cons

Erlang-Centric Design

Tightly coupled to the Erlang/Elixir ecosystem, making it inaccessible for teams using other programming languages and limiting its broader adoption.

Documentation Fragmentation

Key documentation is hosted on external sites (e.g., ws.n2o.dev), leading to a disjointed learning experience and increased effort for troubleshooting and setup.

Modular Setup Complexity

Being embeddable and modular, configuring N2O involves setting up multiple components and protocols, which can be cumbersome for rapid prototyping or simple projects.

Frequently Asked Questions

Related Projects

phoenix

Peace of mind from prototype to production

Small, fast, modern HTTP server for Erlang/OTP.

Stars7,521

Forks1,173

Last commit7 days ago

Ash Framework

A declarative, extensible framework for building Elixir applications.

Stars2,515

Forks450

Last commit2 days ago

mochiweb

MochiWeb is an Erlang library for building lightweight HTTP servers.

Stars1,889

Forks459

Last commit1 month ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

n2o