# Reasons a company considers replacing its backend technology stack

DevFeed: [Reasons a company considers replacing its backend technology stack](<https://devfeed.tech/articles/why-we-at-famous-company-switched-to-hyped-technology-27357.md>)

Original publisher: [Read original article](<https://saagarjha.com/blog/2020/05/10/why-we-at-famous-company-switched-to-hyped-technology/>)

Published: 2020-05-10T00:00:00Z

Content type: opinion

Language: en

Sources: [Saagar Jha](<https://devfeed.tech/sources/saagar-jha.md>)

Topics: [Back end](<https://devfeed.tech/topics/backend.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [garbage-collection](<https://devfeed.tech/tags/garbage-collection.md>), [latency](<https://devfeed.tech/tags/latency.md>), [rewrite](<https://devfeed.tech/tags/rewrite.md>)

## AI overview

A company describes considering a replacement for its backend technology stack. The stated concerns include latency spikes associated with garbage collection and difficulty hiring developers for its existing language.

## Source excerpt

When $FAMOUS_COMPANY launched in 2010, it ran on a single server in $TECHBRO_FOUNDER's garage. Since then, we've experienced explosive VC-funded growth and today we have hundreds of millions of daily active users (DAUs) from all around the globe accessing our products from our mobile apps and on $famouscompany.com. We've since made a couple of panic-induced changes to our backend to manage our technical debt (usually right after a high-profile outage) to keep our servers from keeling over. Our existing technology stack has served us well for all these years, but as we seek to grow further it's clear that a complete rewrite of our application is something which will somehow prevent us from losing two billion dollars a year on customer acquisition.