Why the Right Technology Stack Depends on the Business Problem
“It depends” is not a cop-out. It is the only honest answer, and here is what it actually depends on.
Ask a room of engineers what stack to use and you will get a fight, or at least a very polite standoff. Everyone has a favorite, usually the one they are most comfortable in or the one they have been wanting to try on someone else's budget. It is one of the most fun arguments in technology and one of the least useful, because the right answer almost never starts with the technology.
The same question, different answers
When I ran SME Nation, I delivered software across a lot of industries, and the stack changed almost every time. A small retailer who needed to update their own site got WordPress and WooCommerce, because the single most important requirement was that they could run it without me. A business with real operational workflows got something custom, because an off-the-shelf tool would have fought them within a year. Same company doing the work, completely different choices, and none of it was about which framework was objectively better.
What decided it was never on the engineering side of the table. It was who would own the thing after launch, what they could realistically maintain, how much money was actually on the table, and how long it had to keep working.
Where these decisions go wrong
The expensive mistakes I have seen were not teams choosing a slightly slower database. They were teams choosing the exciting thing. The framework someone read about that week. The architecture that would have been perfect for a company ten times their size. Then it gets handed to people without the context to maintain it, and two years later everyone is afraid to touch it.
When we modernized Hoppler onto AWS, it was not about chasing the cloud for its own sake. It was about where the platform actually needed to scale, what the team could operate day to day, and what it would cost as usage grew. Boring criteria. They are also the ones that age well.
The questions that settle it
So when someone asks me which stack, I tend to ask back:
- Who maintains this in two years, and what do they already know?
- What happens to the cost as it grows?
- If we get this wrong, how painful is it to change?
Answer those honestly and the technology usually picks itself. The fun goes out of the argument, which is probably why people avoid asking them. None of this means technology does not matter. It means it is the second decision. The first one is understanding the business well enough to know what you are choosing for.
Written by Ronald Patrick G. Wenceslao — Engineering & Technology Leader. Open to leadership, advisory, and AI-enabled operations conversations.