Sails.js vs CakePHP

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

Cake has a built-in ORM which is pretty easy to use and learn. Building queries can also be done very easily and fetching entire columns can be done in one or two lines of code.

Developing in CakePHP is very fast and flexible.

CakePHP is about fast and reliable development, it achieves this by following the convention over configuration principle as it's heavily inspired by Rails (which follows the same programming paradigm).

Convention over configuration is all about making it easier for the developer to start immediately writing code without worrying on what's going on "under the hood".

CakePHP has a large library of helper classes with features such as:

• Authorization
• AJAX
• Forms
• E-mails
• Internationalization
  etc...

Cake's great community has thrown together an exhaustive and amazing list of resources to get started with CakePHP. It's open source and can be found on GitHub.

CakePHP open source and is licensed under the MIT license.