Technical Stack Details¶
Toucan Toco is built with awesome open-source blocks that have proven their reliability and efficiency.
The front-end is only a collection of static files (js, css…).
Those files are generated with the following JS libraries:
- AngularJS as the former application framework, now deprecated in favor of Vue.js
- Vue.js as the new application framework
- D3.js to render charts
- Crossfilter to filter data on multiple dimensions
- LoDash to reshape data
- TopoJSON to create vector maps
It’s built using this set of languages and tools:
We also use Nginx as the webserver of all front-end files.
The back-end is a Python 3.6 HTTP REST API mainly powered by:
- Flask as application framework
- Pandas for data processing
- Celery as distributed task queue
- Dask as parallel computing library
Many other python libraries are used for databases connections, access rights, etc.
It also uses Node.js for some operations such as compiling CSON configuration files to JSON.
With the details given above, the full workflow will be as following:
- all connections are in HTTPS (the connection between Nginx and the Toucan Toco App is over HTTP but it’s through a local socket).
- if the Toucan Toco backend is installed in a private network, an outside client will not be able to reach it and access the data. The client should be inside the private network or use a VPN connection.
- the Toucan Toco frontend is only static assets (js, css, html…). There is no data on the frontend side.
Typical Sequence Workflow¶
To complete the previous schema, please find the typical sequence workflow between the Toucan Toco frontend, a client and the Toucan Toco backend.
- The client (browser) downloads static assets (js, css, html…) from the Toucan Toco frontend by HTTPS.
- Then the client only talks with the Toucan Toco backend by HTTPS. The only data stream is between the client (browser) and the Toucan Toco backend.
- There is no data stream/flow between the Toucan Toco frontend and the backend.