PRP
  • PRP Documentation
  • Introduction
    • Glossary / Terminology
    • Indicators
      • Disaggregations
      • Calculating progress
    • FAQ
    • Releases / Changelog*
    • Report an Issue / Contact us
  • Product / End-user Documentation
    • IP Reporting
      • Overview
      • Partner roles and permissions
      • User Interface
      • Setting calculation methods for indicators
      • Progress Reports
        • Reporting Overview
        • Special Reports (SR)
        • Humanitarian Reports (HR)
        • Quarterly Progress Reports (QPR)
        • Reporting Process
        • Data Uploader for QPR and HR
      • Various data exports
    • Cluster Reporting
      • Overview
      • User Authentication, Roles and permissions
      • AD Integration
      • Response Plans
      • Cluster Indicators
      • Response Plan Dashboard
      • Response Parameters setup
      • Planning your action as a Partner
      • Reporting on results
        • Reporting to UNICEF
      • Analysis of results
      • OCHA Integration
    • ID Management
      • Overview
      • AD Integration & Sign In
      • Email Notifications
      • User Statuses
      • Permissions
      • IP ID Management
        • User Interface
        • Users screen
      • Cluster ID Management
        • User Interface
        • Users screen
        • Partners screen
  • Technical Documentation
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Data Model
    • API Documentation
      • Error Handling
    • CartoDB location sync
    • OCHA Integration - Research Summary
      • Response Plan Import
      • Project Import
    • ID Management
      • Backend API's
    • Handover session question
Powered by GitBook
On this page
  • Data Flow
  • PRP <> PMP
  • Services
  1. Technical Documentation

Architecture

PreviousPartners screenNextDevelopment Setup

Last updated 6 years ago

Data Flow

The flow of data between PRP and any external systems is document here.

PRP <> PMP

The diagram below represents the integration between PRP and PMP. Arrows represent the direction of data flow. PRP polls PMP for data on a regular basis. For indicator / progress reports etc. PMP makes live calls to PRP, directly from the users browser, using JWT tokens to authenticate / authorize. This helps reduce complexity of integration and also make it less bug-prone.

Services

The platform is structured such 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 a readily available Docker image that we configure for our own use.

The implementation details of each of these services is as follows:

  • 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

PD Sync in Dev environment happens every 30 minutes (). Demo is 45 minutes. These can be configured/changed if needed.

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

Polymer frontend - This is the SPA written in .

#994
Django
Django REST Framework
Polymer
Arrows represent the direction of data flow