Skip to content

Latest commit

 

History

History
60 lines (45 loc) · 4.45 KB

README.md

File metadata and controls

60 lines (45 loc) · 4.45 KB
Raw

IUDX

iudx-deployment

This repository gives installation and setup scripts to deploy the IUDX platform. We provide and support two types of IUDX platform deployment :

  1. Docker Swarm based deployment
  2. K8s based deployment

The IUDX platform consists of various IUDX-built services and open-source components. The overview IUDX platform with components is shown in the below figure.

IUDX is a data exchange platform facilitating the seamless discovery, and exchange of authorized data. Following is a short explanation of how various components interact in the IUDX platform:

  • Through the IUDX Catalogue server users discovers different datasets available on the platform.

  • A user can register with one or more roles (consumer/provider, data ingester/delegate) in IUDX AAA and keycloak. The keycloak is used to manage the identities of users.

  • The user can get set/request policies at the AAA server, and get a token. IUDX AAA platform manages the policies through credentials/Policy Datastore(Postgres).

  • Through this token, the user can publish(input)/consume (output) data from any of the IUDX resource access services (resource server, rs-proxy, GIS server, Data ingestion server, File server)

  • IUDX platform supports the following input data flows

    • A data ingester ( delegate ) can pull the data from the downstream source (ICCC) and push it to the databroker (Rabbitmq). Which then is consumed by Logstash, the latest ingestion pipeline, and is pushed to the Meta Data/Data Store (Elasticsearch) and Latest Datastore (Redis).
    • Also a data ingester can directly push data through HTTPS APIs exposed by Data Ingestion Server.

  • IUDX platform supports the following output data flows

    • Get data through standardized Resource access service APIs - spatial, temporal, complex, file, gis, and async queries.
    • Get live streaming data through Rabbitmq using a resource server Subscription
    • Get data from non-IUDX resource server through resource-server proxy (rs-proxy). This is done through IUDX RS API query translation to non-IUDX RS-specific queries by a set of adapters that reside close to non-IUDX RS. The query and response are communicated to adapters and rs-proxy through databroker(Rabbitmq).

  • IUDX platform is monitored through the micrometer, Prometheus for metrics and promtail, Loki for logs, and Grafana for Visualisation

  • The alerting through SMTP server for emails or Telegram bot for telegram messages.

  • All HTTPS API requests are processed through the API gateway.

  • The Rabbitmq specific communication i.e. streaming of data through AMQPS and HTTPS management interface is through the streaming gateway

  • Hazlecast with Zookeeper is used as the cluster manager for all Vert.x based API servers.

  • Successful API calls are audited in tamper proof database - immudb and in postgres through an auditing server

To know more about IUDX, refer following resources:

  1. What is IUDX? To get an overview of the IUDX platform and its main motivation
  2. IUDX Architecture Overview
  3. IUDX Developer Section

Features

  • Service Mesh Architecture based Vert.x API servers.
  • Each microservice is a well-defined module that can be containerized and discovered using service discovery.
  • Docker Swarm deployment enables easy, cost-effective deployment of the IUDX platform suitable for prototyping and PoC.
  • Kubernetes-based deployment of the IUDX platform gives a scalable, highly available system through the clustered deployment of each component. It's suitable for production-grade deployment.
  • Both docker and K8s-based deployment is cloud agnostic* and can be deployed on any cloud or on-prem. It has been tested currently on AWS and Azure.

*Note: K8s deployment depends on certain cloud services - Load Balancer, Storage, Object Storage, K8s cluster autoscaling but since this is offered by major clouds. It can be integrated into these cloud providers.

Contributing

We follow Git Merge based workflow

  1. Fork this repo
  2. Create a new feature branch in your fork. Multiple features must have a hyphen-separated name, or refer to a milestone name as mentioned in Github -> Projects
  3. Commit to your fork and raise a Pull Request upstream.
    Detailed instructions are present here.