The article advocates for purchasing a fastThread subscription despite infrequent use, comparing its value to vital surgeries. It highlights fastThread's role in minimizing costly production downtimes, safeguarding brand reputation, facilitating swift problem resolution, and promoting sustainable stability through deep JVM analysis, ultimately enhancing operational efficiency for organizations.
The article discusses the optimal strategy for application memory sizing: large memory with few instances or small memory with many instances. Two successful technology companies exemplify contrasting approaches. Both strategies can succeed, depending on team competence. Large memory is more expensive, but business needs may dictate memory requirements. Experience and emotions influence decisions.