Dapr-Distributed-Application

A Dapr application made up of a React/Express front-end and a Flask back-end in self-hosted mode with Docker-Compose. Envoy is used as a proxy to the rest of the containers - with the entrypoint being set to port 10000. Currently developed to be ran in self-hosted mode.

Project structure:

• frontend:
  • A React application which utilizes Express to serve it's static files and run server side calls to make use of its Dapr sidecar.
  • Uses Daprs service invocation which calls to Daprs frontend sidecar. This call invokes the associated endpoint on the backend service which is used to retrieve a list of bikes from Azure Database for PostgreSQL.
  • Uses Daprs secrets API to retrieve secrets for a local environment Secret Store(.env file).
• backend:
  • A Flask application which retrieves data from Azure Database for PostgreSQL and returns this to the frontend to be displayed.
• components:
  • Dapr components are defined in this location.
  • config.yaml is defined to utilize Dapr distributed tracing with Zipkin
  • localsecretstore.yaml is defined to utilize the local environment variable secret store.
• envoy:
  • Envoy and it's custom envoy.yaml is defined in this location.
  • The Dockerfile is used to pull Envoy's image while envoy.yaml has a custom configuration that is copied over to the containers default configuration for this project
  • In this example, requests are proxied via Envoy on port 10000 to the other containers(services). Additionally, and example of how to remove headers have been added. So far removing the x-powered-by header in the envoy.yaml.