Sails.js vs CaptainCasa Enterprise Client

Sails.js is built with a focus on building real time communication apps such as chat or multiplayer games, so naturally it has Socket.io extremely well supported.

This could be a huge plus, if you prefer to build your apps using the Model View Controller architecture. Using Sails.js you'll find the task of separating the business logic from the user interface and keeping the interactions between them in a separate layer, extremely easy.

Exposes public JSON API for free. No additional routing to be defined. Makes it pretty easy to access data from anywhere.

Sails.js uses Waterline ORM at its backend which means you can store your data in any datastore that you like; all you have to do is make a change to the Waterline adapter, this will allow you to store your data in MySQL/Redis or any other kind of database.

Clear documentation and easy to understand. The file structure gives you a way to understand where you can start to develop when you encounter a new Sails project

Very fast even with many controls. CaptainCasa Enterprise client is much faster than Vaadin when writting similar programs.

Separation of the backend code and the creation of the pages / Injection of the code (CDI) into the pages via expression language (EL).

No javascript is needed, everything is developed on the server with Java. Optimized roundtrip.

In addition to the extremely good performance, which already ensures that the system can be scaled well, clustering of the system is already provided for in the software architecture.