Bran-write

Service that watches the Platform and gathers statistics: messages counts, threads, containers starts/stops. Collected data is stored in the Clickhouse and accessible by the Bran-read service’s API.

• Downtime
• Scaling
• Deployment
• Strong dependencies
• Weak dependencies

Downtime

Not critical

Bran-write down means delayed statistics in the Clickhouse. After start it will process delayed data. Forbidden to shut down for long time (e.g several hours). It may cause queue overflow in the RabbitMQ, and a risk of data loss.

Scaling

Scalable to any reasonable amount.

Deployment

Use rolling release. Update pods one by one.

Strong dependencies

Bran-write strongly depends on the Clickhouse and the RabbitMQ. It will not start without them.

Weak dependencies

Bran-write would not function without the Admiral.