Tines - Fargate architecture

Fargate architecture overview  

The below image outlines the high-level architecture of Tines when hosted with Docker compose

Tines Fargate architecture overview

Explanation of steps  

  • R1: The user's browser or a webhook initiates a request

  • R2: TLS Termination happens at a load balancer level

  • R3: From the load balancer, the traffic is sent to the Tines web services,tines-app

  • R4: tines-app which is a web service, communicates with PostgreSQL for storing and reading persistent data

  • R5: tines-app then schedules background jobs to process any action runs in a Tines story. it enqueues the job details in Redis

  • R6: tines-sidekiq, which is a background queue service, then picks up the jobs that are enqueued in Redis and performs further processing. tines-sidekiq then picks up jobs that are enqueued in Redis and performs further processing

  • R7: tines-sidekiq communicates with PostgreSQL for storing and reading persistent data

  • R8: tines-app and tines-sidekiq accordingly make requests to external APIs and endpoints for further processing in a story and actions

Was this helpful?