Put simply, a real-world application needs more than GET, POST, PUT, DELETE. Real-world applications use more than just HTTP. How about WebSockets? MQTT? Events? Notifications? With REST your API is bind to HTTP.

Let’s stop pretending REST is a good idea. REST is a bad idea that twists HTTP into something it is not, only to work around the limits of the browser, another tool twisted into being something it was never meant to be. This can only end in tears.

• Mike Hearn

• ~250ms startup time for simple demo application worker
• Under 1s startup time for real world application cluster with 8 workers
• Secure built-in authorization with cryptographic passwords hashing bcrypt, JSON Web Tokens (RFC 7519) encoding/decoding
• Simple modular extensible architecture to build complex RPC APIs. (Code base in production since 2013)
• Request and response data validation using declarative style API and JSON Schema validator (ajv)
• Simple error handling
• Built-in API auto discovery
• Simple test tools (mm-test)

1. Getting started — explanations of framework's architecture and a tutorial with all the steps to make an application from scratch
2. Clone the demo application.

• Units
• Protocol
• Settings
• Extensions
• Transports
  • HTTP
  • WebSockets
• Serializers
  • JSON
  • MsgPack
• API and Resources
• Authentication
• Cli
• Errors codes

License: MIT.