Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
C0D44768286dI'd normalise it in a db and then work with the data from there.
Maintain or automate a regular update (weekly/monthly) and then sell it back to them in the form of an api 😏
Now hurry up before someone else does it.
Reason is portability...
Depending on the export (don't know the transit thing you mentioned) the file format will never change after being released once.
Many many many companies still use ASCII instead of UTF, which is even worse than the file format.
Always. Really always. Abstract the import of your data from the data layer that you want to use. And Abstract this layer from the Services that consume the data.
It might increase the work load at the beginning, but it solves many many many problems afterwards.
When you design the data layer, especially when utilizing a database, ignore the format of the file.
Let the importer service prepare the content, transform it to your needs and then let the data layer handle validation, consistency checks and persistence.
Always expect surprises :)