4 ms·
> Once you update, its hard to make sure you caught every single business rule and weird edge case from your old system One of the reasons we're trying to migr
by boobsbr 12y ago
> Once you update, its hard to make sure you caught every single business rule and weird edge case from your old system
One of the reasons we're trying to migrate our rules to a rules engine. They're scattered across pages, Javascript, controllers, services and DAOs...
No one knows all the business rules of the system, not even the BAs.
- robalfonso 12y agoExactly, we obscure all the weird registry stuff behind an object it figures out what it needs to do that's different. Billing system is the same way. Though the real difficulty is that so much of it is configuration (in the registrar space). Piles and piles of xyz happens on day 30 for this tld, day 5 for this one,etc. Also of interest is that not all registries even support the standard set of commands for updating domains/contacts/nameservers which is quite obnoxious.
- sanderjd 12y agoIt seems like the hardest (or maybe just most tedious) part of this sort of thing is keeping the rules on the front-end and the rules on the back-end consistent. Obviously the back-end needs to be the canonical source of truth, but it's nicer for the user if the front-end knows the rules too so that it can do the right thing prior to a full request cycle. I'd be interested to know if you've come up with a good solution to this, because I haven't found any that are very satisfying.