Architecture

Services

The platform is structured in a way that all the functionality is exposed via REST API's. The data from these API's drives the web interface which is a Single Page Application (SPA). There is a proxy that sits in front of the frontend SPA and backend API's. Additionally there is a message broker and asynchronous task / job queue that is used to run long-running and regular (say, every 1 hour or 1 day) tasks.

Each of these services is either in the code and has an associated Dockerfile describing how it can be built and deployed on a docker friendly environment. Or this service uses alreadily available Docker image that we configure for our own use.

The implementation details on each of these services are the following:

• Django API - This is the backend REST API service. Uses Django and Django REST Framework.

• Polymer frontend - This is the SPA written in Polymer.

• Nginx proxy - This sits in front of the Django and polymer services and routes requests. This helps us to not run these services on different ports, for example, that would cause CORS issues.

• Redis

• Celery Beat

• Celery workers

• PostgreSQL database