Symfony vs. Tornado vs. Sane Stack

Backend and MVC framework.

The RESTful backend for Hilenium was built using the Symfony2 framework.

Solid components backed by a great community and visionary company (sensio labs).

Base framework

website backend

Web-framework con el que se desarrolla la aplicación ITBID

Symfony provides a relatively small piece of the puzzle. Its biggest contribution: the gapi services (and other remote APIs) are configured with server-to-server service account access. Sym3 provides an endpoint that returns a svc acct access token that's - in turn - used by Ng2 to authorize the remote services.

Back-end Framework, data model implementation, Database interactions.

Backend for RESTful API.

Symfony is a set of PHP Components, a Web Application framework, a Philosophy, and a Community — all working together in harmony A framework is a collection of universal, reusable programs that accomplish particular tasks to facilitate the development of software applications. A framework is a pledge of quality, upgradability and maintainability of applications at lower cost. Applications developed using a framework are interoperable with market standards.

We switched to SPA. No need for this.

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.