I serve near StackOverflow levels of traffic. Similar # of page views and more than 5x the egress bandwidth. Also .Net. Also running a traditional monolith sty

I serve near StackOverflow levels of traffic. Similar # of page views and more than 5x the egress bandwidth. Also .Net. Also running a traditional monolith style system. One main SQL DB. Another for some logs. Redis. Blob storage. KISS. We have various miscellany and a dozen+ web apps for public website, internal admin, content editing, monitoring, on-the-fly image resizing, etc. but even the API's serving those live in one web app, and our high traffic data & content service is just one app. Nearly everything in one solution and repo. Tbf, we've been utilizing chromium more over the past year and I think we're going to have to split that out into its own service. We do a lot of data-driven image generation and used a couple .Net imaging libraries for that until last year. Since then we've been building new data-driven content solely in HTML/JS and screenshotting through chromium to generate static images (we serve the same content in animated HTML and JPG and used to build each separately).