Skip to content

Arch Forum 2024-03-07

Participants: Backend devs, Zak, Magnus, Victor and Andy

Agenda

  • Automapper part 2
  • DB migrations

Notes

Automapper part 2: Meeting started with a short discussion around Automapper and mapping in general. Victor had done a short inventory of the special features we use. There are 2 mapping validations: Sensitive data (which is probably useless the way it's used), and of our custom validation attributes (CurrenyIdAttribute, MsisdnAttribute etc) which has a buggy implementation. WE also have a custom Enum mapper, which probably accounts for a large portion of performance of the mapping done.

Regarding mapping libraries, in general, we want to have a single way to handle object mapping. It is difficult to motivate to switch mapping library because of the time needed. A new library even with API similar to AutoMapper is likely to have hidden issues needing custom solution. Therefor, the decision is to stay with AutoMapper and instead try to update it to latest verison.

DB migrations: From the Bank & Risk team retro, Zak raised the topic of DB migrations, and specifically that it's difficult to manage the Stored Procedures with our current setup. A shorter discussion followed. It is an important issue, and it's already among the top priority things. What is missing is that someone take the time to make a concrete suggestion (with code) how to improve. Unfortunately Victor does not have time at the moment, but its open for others to look into as well.