Hapi vs FeathersJS

Hapi was developed and is still being used by Walmart. Being backed by such a major company means that it will not lose support any time soon and most importantly it's being developed by professionals and that you will always get support for it.

Hapi's philosophy is that configuration is more important than code. This is especially useful for very large teams because it helps developers maintain consistency and reusability throughout their code.

Feather can sync events happening in two different Node processes or even servers in real-time. For example: an event happens in server A, the user connected to server B is instantly notified of that event.

This is done through a central Redis or Mongo collection or through a websocket libraries' clustering library.

Through services, Feathers provides instant CRUD functionality, it also can easily expose a RESTful and real-time API through HTTP/HTTPS and websockets.

Since Feathers itself is built on top of Express (it's a thin wrapper over socket.io, primus and Express) and because of Feathers' highly modular nature, it's very easy to integrate Feathers in an existing Express project.

Feathers makes extensive use of modules (which are called Feathers services). These services work like ExpressJS middleware and can be used with app.use('/path', serviceObject).

Services help developers keep their applications modular and as minimal as possible, without any unnecessary libraries or bloat.

FeatherJS uses primus which is a universal wrapper for real-time frameworks. Through primus you can easily choose which socket transport you want to use.