Arch Forum 2026-10-02

Participants: Backend devs and Victor

Agenda

• Platform news
• Config automatic reload
• Rebtel + Majority
• LithicTesting Demo (Shakib)

Summary

Platform news

• [BCP-3598] Make RabbitMQ shutdown graceful / Shakib
• [BAN-387] Add transactional outbox publishing via OutboxOptions / Shakib
• [BCP-3600] Add optional per-method SQL command timeout / Shakib
• [BCP-3602] Make flexible enum member registration thread-safe / Shakib
• [BAN-420] Add optional cancellation token to SQL repository methods / Shakib
• [BCP-3604] Add optional cancellation token to Firebase repository methods / Shakib
• [BCP-3605] Skip the Firebase conflict delay after the final write attempt / Shakib
• [BCP-3606] Emit valid stubs for unsupported Firebase repository methods / Shakib
• [MIB-14340] Replace FluentAssertions with AwesomeAssertions
• [MIB-14339] Replace SQL naming validator with generator enforcement

Config automatic reload

Today we automatically reload config files in the config loading library in be-platform. But then it depends on the exact usage of the config class if the updated config will actually have any effect on the logic. Since this is quite hidden, should we remove the feature all together?

Notes:
- If we would automatically restart on config syncs, then in some special cases it might be good to be able to skip the restart. E.g. deploy new config, no restart of old code, then deploy new code. Then the updated config only came in effect on the new code, for "free".
- In some cases its clear what needs restart or not, but in many cases its not. One especially tricky case is global configuration changes that require a restart today. Very easy to miss restarting some service.

Rebtel + Majority

A short info about joint sharing projects:

1. Rebtel and Majority both use (Majority) Simon (dt-ai-agents repo).

• Shared repo, dt-ai-agents
• Two instances of simon deployed Simon and Sophie.
• (Majority) Hydra manages articles in both instances here. Given sufficient permissions a user can toggle between managing Majority or Rebtel articles.
• Each instance has its own DB, KV etc.

1. We want to unify so that rebtel uses (majority) risk (be-risk repo).

• Shared repo, be-risk
• Details to be decided.

LithicTesting Demo (Shakib)

Shakib show how we handle regression testing involving the 3rd party Lithic, which uses the special LithicTesting service (still in the be-lithic repo). This is a useful technique for working with third-party providers that have limited or unstable testing environments.

Slides here