Skip to main content
Version: Current (3.x)

Repositories

This page lists the repositories that are part of the data-viz infrastrcture

1. Data VIZ UI​

  • This repository contains the frontend code of the data-viz infrastructure. It is built using React, Typescript and Redux.
  • It consists of the following modules:
    • @devgateway/dvz-ui-react - This is the main module that contains the UI components that are used in the frontend.
    • @devgateway/dvz-ui-react-lib - This module contains the custom library that is used by the UI to interact with the Wordpress API. This is also a submodule that can be found here

2. Data Viz Wordpress​

  • This repository contains the Wordpress code of the data-viz infrastructure. It is built using Wordpress, Typescript and Redux.
  • It consists of the following modules:
    • wp-react-blocks-plugin - This module contains the custom blocks that are used in the Wordpress editor.
    • wp-react-blocks - This module contains the custom blocks that are used in the Wordpress editor.
    • wp-react-custom-multilang - This module contains the custom multilanguage support that is used in the Wordpress editor.
    • wp-react-custom-rest-menu - This module contains the custom rest menu that is used in the Wordpress API.

3. Data VIZ API​

  • This repository contains the backend code of the data-viz infrastructure. It is built using Java, Spring Boot and Postgres.

  • It consists of the following modules:

    • api-gateway - This module contains the API gateway that is used to route the requests to the appropriate microservices.
    • api-security - This module contains the security logic that is used to handle Login and Authentication.
    • registy - This modules contains the microservices registry that is used to register the microservices. It uses Eureka as the service registry. You can read more about Eureka here
    • commons - This module contains the common code that is shared by all the microservices.
    • superset-proxy - This module contains the superset proxy that is used to proxy the requests to the superset server.

  • You can use any of the services depending on your requirements.