Sails.js vs hapi: What are the differences?

# Introduction

1. **Request Lifecycle Handling**: In Sails.js, the request lifecycle is based on the MVC pattern where controllers handle the logic for incoming requests. On the other hand, hapi provides a more flexible approach to request handling by allowing developers to define routes with their own configuration options and request handlers.
2. **Real-Time Communication**: Sails.js provides built-in support for WebSockets and real-time communication through its WebSocket library, making it easier to implement features like chat applications and live updates. In contrast, hapi does not natively support WebSockets, requiring developers to use external libraries or plugins for real-time functionality.
3. **Waterline ORM vs. No ORM**: Sails.js includes Waterline ORM as the default database layer, providing a unified API for interacting with various databases. Meanwhile, hapi does not come with an ORM out of the box, allowing developers to choose their preferred database library or ORM for data persistence.
4. **Configuration and Flexibility**: Sails.js follows a convention-over-configuration approach, where certain configurations are predefined and can be overridden as needed. In contrast, hapi offers a more explicit and configurable setup, allowing developers to define the server, routes, plugins, and other components with more control and customization options.
5. **Plugin Ecosystem**: Sails.js has a robust plugin ecosystem that offers a wide range of pre-built modules for extending the framework's functionality. hapi also has a plugin system, but the number of available plugins may be relatively smaller compared to Sails.js, requiring more custom development for specific features.
6. **Performance and Scalability**: While both frameworks are known for their performance, hapi is often considered to be more lightweight and focused on efficiency, making it a preferred choice for projects where scalability and speed are crucial factors. Sails.js, on the other hand, provides more out-of-the-box features and conventions, which can sometimes impact performance depending on the project's requirements.

In Summary, Sails.js and hapi differ in their approach to request lifecycle handling, real-time communication support, ORM usage, configuration flexibility, plugin ecosystems, and performance emphasis.