CodeIgniter vs. Tornado vs. Padrino

CodeIgniter is the MVC framework used for the PHP coding. Also, validation criteria for (database) table fields are the provided by CodeIgniter, and signatures for others are derived from those.

I used CodeIgniter while working at KHM Travel Group. It was the system we used for an affiliate-based site called TravSearch, which I later replaced with a WordPress Multisite. I developed a .csv upload form to transfer all the information from the affiliate table of CodeIgniter to the user and options tables in WPMU.

Integrate with some code-igniter low-level modules through composer.

It is super easy to do things in PHP using codeigniter. Used the MVC architecture to create different types of pages and modules.

Old stack framework

We use Tornado as our websockets server, using SockJS (an alternative to socket.io).

SpreadServe's RealTimeWebServer is built in Tornado. Spreadsheets loaded into SpreadServeEngine instances are projected into browsers using Tornado. Server side recalcs are pushed to the browser using web sockets.

Tornado with Async/Await coroutines provided in Python 3.5 make up for an excellent stack for a micro-service.

setup an api for a client with tornado backend. incredibly fast and lightweight. unfortunately breaks down when using third party libraries which block internally.