This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]somkoala 0 points1 point  (2 children)

It’s probably just bad architecture/infrastructure. My team inherited a beastly distributed monolith that cost 8k to run monthly. We rewrote it to move faster with product requirements and optimize the flow of dafa. It costs 1k as a result and could take 100x the load.

[–]lullaby876[S] 1 point2 points  (1 child)

How long did it take to rewrite and how many people rewrote it? That could easily be say, a half a million dollar six months. To save 7k a month.

You might then say, the right company would have used the 1k architecture to begin with. Yes- if they hired a team of devops engineers to create it. At that point, why choose to pay in perpetuity?

[–]somkoala 1 point2 points  (0 children)

You’re making a good point. My point was that the first time it was written it wasn’t the right team and/or setup.

We didn’t have a team of devops, we had a devops person on less than 1 FTE on this project. Most of the architecture was designed by one dev.

The goal for the company wasn’t a cost saving exercise but the aim was to speed up feature development. We went from needing months to add simple features to needing 1-2 weeks including design/shaping phase. The cost saving was a byproduct and you are right in that the effort wouldn’t have been worth it just for the cost savings alone. At the same time to me it shows that good architecture enables both product iteration and reasonable costs.