Building a High-Volume Push Notification System - (1) The Beginning

While feeling bored with B2B services, I moved from the B2B service team to the B2C service team at the recommendation of my company's director.

#The Beginning of the Problem

I stepped into the B2C service server developer position that had been vacant for about 6 years, and as I somewhat expected, the problems from the vacancy were bigger than I thought.

<What came to mind after receiving all the server code>

When I first joined the team, there were really many problems, but the biggest issue was that there was no push notification system, so the client developers were barely keeping the service running with band-aid fixes.

Was there no problem with running it this way?

Of course, there were many service-related problems, and as a result, many negative experiences were being exposed to users.

From a cost perspective, there were also many inefficiently used expenses.

Also, looking at our team's 2020 roadmap, a push server was not an option but a requirement.

There were various improvement plans, but the development of a high-volume integrated push server became the top priority.

It was very unfortunate that a service with the potential to grow like a rocket was being held back by the lack of such basic infrastructure.

#Starting This Series

Trying to tell this whole story in one article would require too many omissions, and I wanted to record my struggles more vividly on the blog, so I decided to write it as a series.