Backend Structure & Servers Configurations

Brain Storm:

• We must use CDN for DNS level load-balancing

• Ingress must have xN replicas, nodePort in multiNode

• "Storage" app svc and storage like app svcs must be stateless with using DBs

• App stateless services must have multi instances (minimum 2)

• Separate client side request from web-socket and using SSE concept for sending server events to client;

  • Client sends HTTP requests

  • Server sends web-socket messages(events)

• Removing kafka from communication level of services

  • Using gRPC for communication

• We can go on some approaches on managing and maintaining stateful services;

  • Dedicated cluster

  • In K8s with CSI

  • DBaaS

  • The goal is using Dedicated cluster or DBaaS approach but for now we use In K8s with CSI approach

• We must remove using Redis as a DB in our backend services and replace that with a persistent DB

  • Remove saving states in Redis on Gateway service

  • Remove saving message-view-count in Redis on message service

Current/Old Architecture

New Architecture

App Server

Notes:

• DEDICATED SERVER

• RAID-1 Hardware level configuration

• CPU with high rate single thread performance

• Good Iran IP! like 5.160.146.*

DB Server

Notes:

• DEDICATED SERVER

• RAID-1 Hardware level configuration

• CPU with high rate single thread performance

Media Server

Monitoring

This server includes logging, tracing, metrics, analytics, sentry infra data.

General Registry

Docker (Registry and cache layers), HELM, NPM, Gitlab Runners and etc.

Notes:

• VM in out-of-country or with active proxy

Test