In this chapter, once we had covered every possible cost-saving implementation in terms of the infrastructure, we started analyzing our application catalog to understand how and why optimizing at the application level is sometimes the only way of bringing extra cost saving to your process.
We started with database tuning and optimization by providing an optimization plan template. Then, we looked at what technical debt is and how to understand, analyze, represent, and reduce it so that your application set is continuously enhanced and improved by keeping costs down. We discussed the importance of an APM tool, such as Azure Application Insights, not only to manage your application at a technical level but also to spot issues that may incur unexpected costs.
We then worked on a few practical examples, starting with an application where we moved the database to NAS (first IaaS, then PaaS), then migrated the database to PaaS, to increase efficiency and cost-effectiveness...