3 ms·
I came here to say this. This is a case of bad design and it goes beyond database constraints. One, as you mentioned, the database schema seems to be driving t
by partisan 8y ago
I came here to say this. This is a case of bad design and it goes beyond database constraints.
One, as you mentioned, the database schema seems to be driving the functionality, not the other way around.
Two, the application is a monolith in the worst way possible. Marketing and order entry are two completely different domains. Pigeonholing then into one means you don’t exactly capture the requirements of either domain correctly.
The discussion is a good one to have, but it needs to happen at a level above where it currently is.