Arch Forum 2023-05-26

Participants: Johan D, Liangxiong, Thani, Victor and Zakarya

Agenda

• Round the table
• Redis
• Platform / Infra code

Notes

Round the table: Liangxiong brought up a case where he wanted to have a folder of config files, to be able to split up one array of config values over an non-predefined amount of files. This is so the Risk decision point config could use a separate config file for each decision point , instead of keeping them all in a single file. In this way the developer that wants to update a single decision point config could easily change a single file, with no risk to change other files. However, after discussion we did not find that the motivation to add such complexity to configs was worth the effort if at all desirable.

Redis: As a follow up on the presentation I (Victor) did on Monday about DB usage we had a short discussion of our Redis usage and could quickly agree that so far we do not get any real benefit from using Redis, and the only result is additional complexity in platform code, infra etc. Therefore, we should not add any more usages of Redis, and if there's an opportunity to remove the uses we have today.

(Obviously there might be cases in the future which could motivate Redis or similar tech, but then we need to really evaluate if its needed first)

Platform / Infra code: Last but not least the topic of platform code. What should be there vs outside and how can we maintain it going forward. No real conclusions came out, we agree that it is an important piece of the backend, and it is important we create a good structure for its future maintenance.