4 ms·
In my experience the majority of enterprise service applications and smaller few-purpose systems are build following 1. We’ve have an ASP Web Forms food orderi
by moksly 7y ago
In my experience the majority of enterprise service applications and smaller few-purpose systems are build following 1.
We’ve have an ASP Web Forms food ordering system that’s basically four forms and a simple CRUD admin system page that’s been running flawless for half a decade. It’s only needed upgrades to its .NET system as we moved up the TLS version ladder, and it has thousands of daily users. There are no tests, no real monitoring outside of “is it still up?” and no complaints.
Eventually we’ll have to clean up the database, eventually. But chances are someone will have build something new by then.
- jaclaz 7y agoMaybe in this specific case there is also a factor of simplicity, simple designs, made with few elements, tend to be more robust, as a general rule.
- moksly 7y agoWe have 50 such systems, most don’t see the “thousands of users” a day though.
- bluecmd 7y agoI doubt that would be 1 and not developed using 2 followed by a "don't touch" policy, tbh
- imtringued 7y agoWe have one project under a don't touch policy. Sure it is probably the most stable project because no features are getting added but it is also becoming a maintenance nightmare the longer we accumulate interest on our technical debt. There is a version 2 planned that will add a lot more features and I'm sure we will spend the first weeks on upgrading the libraries it is using because they are a major version or two behind.