What's the engineering cost to move the dynamic site over to a static site and fix any issues there within when you have no engineers working on staff anyway. W

What's the engineering cost to move the dynamic site over to a static site and fix any issues there within when you have no engineers working on staff anyway. What's the ongoing price of dealing with things like legal threats take down notices etc. Especially when you have no engineer and no good way to just go remove individual pages or deal with those types of issues. What's the engineering cost to go deal with changing regulations like gdpr and right to be forgotten we need to go remove comments or other user posted information from someone. What is that giant mess going to look like and how do you get an engineer to spin up on it fix each of those things on a one to two year timer probably in between any given issue. How excited is that engineer going to be a 3 to 6 months break in something that's actually useful to their career to go patch someone else's tech debt. What level of quality of work does that lead you to get. Where do you even put the headcount for an engineer or who do you steal them from that is less important than a dead archived website that's been sitting around for years. All in I think a base level engineer at Amazon probably makes around 250 to 300 when you include all the support in for a and all of the benefits and everything else. That's for an entry-level engineer who probably will have trouble understanding the weird ass bespoke infrastructure that has been created for this one-time thing in a dead corner of the company. Well you may not agree with any of these things these are all considerations that would go into a decision like this and all the complications this is not some shit just running on your digital ocean droplets and it's all things that companies have to take into consideration when they are the size of Amazon and have a Target on their backs for regulators and lawsuits. No I'm not saying either way if I support or don't support this decision all I'm saying is all these things would go into consideration into a decision like this from just a pure engineering level. I've sadly had some projects that I worked on in the past were they looked at it and they didn't want to do archival because there was just not worth the legal risk to deal with changing laws like gdpr so they just shut the feature down. This is often the calculus that happens how much revenue is it making what is the legal liability risk of keeping it up what is the ongoing engineering cost to maintain it or spin up an engineer and fix it in between. Given that 300K price and just assuming you got to do one year of fixes over the next 10 years that site better be bringing in multiples of $300,000 a year in revenue to even make it worth it to not just shut it off. Esp if you can't quantify community good will. Personally one of the lessons I learned is if I build a system like I did for gaming again I will make it so that we can shut it into a top and list archival mode that can be run minimally from a CDN but sadly I didn't think of that when we built it and it was a little expensive to do it the right way after the fact since I was the only one that actually understood the tech.