Skip to content

Arch Forum 2023-08-17

Participants: Andy, Liangxiong, Shakib, Thani, Victor

Agenda

Notes

SMS / notification service The first topic discussed were what to do with sending SMS (MIB-7953). Today, SMS is used for OTP/login and transactional messages to users. Sending OTP code is done with Sinch & Infobip third parties through user area, while others are sent through Braze. However, Braze will not allow transactional SMS through their service anymore.

After discussion, it became clear that the best way forward is to create an SMS area that handles the integration with Sinch & Infobip, and move over both the Braze SMS sending and OTP sending in User to this new service. More details in https://dev.azure.com/MAJORITY/Documentation/_wiki/wikis/Main/247/20230817-SMS-Area

Localization in backend Also from MF team, for the Promo FX rate they have need to frequently update localized strings and the question is how to best handle this? (MIB-8153) Currently, we do localizations by committing the localized strings as JSON files to each service's repo.

  1. A localizable string is added to 3rd party Crowdin.
  2. Its translated by external translators
  3. A developer downloads the file, commit it and make a release.

This process is seen and slow and somewhat cumbersome. Several cases were brought up

  • Often times translations are completed after a feature has been completed and merged to master. This means the developer needs to create a new branch, commit, merge and deploy.
  • Promotions for the Promo FX can be updated fairly frequently, and Product wants to be able to manage these independently of tech.

We could not fully conclude the best way, but the most promising seems to be to just create something to make the developer process easier, such as a script that automatically fetch translations and create PR.

A more comprehensive solution would be with a translation service, but that feels overkill.

Braze / marketing Product want to notify users when a FX rate reaches certain values. Details in here: MIB-8499. They also want to show historical FX Rates. The need for historical FX rates is something that Moneyflow/Thani does not agree with, this is information not used by other business logic in the backend but would only be used by the promotion messaging. Therefor, it feels more suitable if the data warehouse could provide this information to Braze.

We concluded that we could not decide this on our own, but should have a discussion with the data team.