@IRJ You are passionate about computers, you love to write code. Well, what's more exciting than being able to create your own plugins.
When you know that WordPress is today one of the most used CMS on the web, it would be really interesting to see how a plugin is made and to be able to create it yourself. [Check it here] (http://bit.ly/2KxPChJ)
I did. We're not ones for forcing tech on clients but there's a limit to client risks that we're willing to live with.
This particular client deals with a LOT of sensitive data and it always bothered me that they had a known vulnerable router in place that we had to admin with a 5 year old version of Firefox.
@DustinB3403 If you (or your customer) are using PRTG, you could use the "cloud ping" and "cloud http" sensors to monitor reachability from around the world. Those sensors will try to reach your website from 5 different AWS data centers, and will report on reachability and response time from each of those data centers. If something goes wrong, you can get an alert, so you know you need to react. The free version of PRTG will let you run 5 cloud http and 5 cloud ping sensors.
If that's not enough, check out services such as https://www.site24x7.com/, which provide similar ongoing monitoring on a larger scale.
I can handle this for you for a flat fee. I promise results within 30 days, or your money back.
Lol. We have to do this the legal way. We are a large company and someone is always trying to sue us. Heck we have people try to send us product we never order then sue us when we don't pay their invoices.
But it's about doing your own cost-benefit analysis. It's too simplistic to say you should never run legacy applications.
Of course, there are always times that legacy applications need to be run. But there are limits too. ASP as a platform has been legacy for a decade and a half. That's a long time. It has a pending end date for when it may not be available any longer in any capacity. It presents platform level risk which may prove to not matter, but may prove to be extremely limiting in the future - that's the nature of risk, we don't know what will happen with hardware and software down the road. But it is technical debt building up in a platform that is nearly all of the way through its "trailing off support" timeframe.
It's fine to have legacy apps. But it is also important to identify when a legacy app is becoming too legacy. In the OP's case, ASP created support and hosting risk in addition to normal concerns. Those were probably types of risk that were not considered in the past. Any business running ASP is constrained if they decide that they want to go hosted, for example. They might not ever decide to do that, but there is technical debt potentially making that decision for them, as well.
Any ongoing support of an ASP legacy app means that investment is being put into the old system. Maybe that is trivial, maybe it is major. Technical debt is a hidden cost. Money goes into keeping the old system running instead of being implemented in a new system. The effort to support the old could offset the effort to replace it.