Choosing a technology stack without the religion
Almost any modern stack can build almost any business application. The differences that matter are who can maintain it, how it is hosted, and how easily it absorbs the integrations you will need.
The four criteria that decide it
Hiring pool in your market. Hosting and operating cost at your expected scale. Fit for the workload, such as real-time, heavy data or offline use. Longevity of the ecosystem, judged by release cadence and commercial backing.
Performance is usually a distant fifth. A well-built application on a mainstream stack will beat a poorly built one on an exotic stack every time.
Boring is a feature
The stack you can hire for in three years is worth more than the one that benchmarks marginally faster today. Boring technology also has more answers written down, which shortens every future debugging session.
Write the decision down
A one-page architecture decision record explaining what you chose, what you rejected and why will save your future team from relitigating it. It is also the first document a new engineer should read.
Common questions
- Should we choose the stack our in-house team knows?
- Usually yes, unless that stack cannot meet a hard requirement. Team fluency compounds; novelty does not.
- Does the stack affect project cost?
- It affects cost mostly through available talent and integration effort rather than raw development speed. A scarce stack raises both build and maintenance spend.
Next step
If this question is live in your business right now, describe the situation and you will get a written view on the options, including whether you should build at all.
Discuss your projectRelated notes
All insightsCustom software or off-the-shelf: how to decide
A practical framework for choosing between configuring an existing product and commissioning custom software, based on where your process actually differs.
ReadStrategyHow to write a technical brief that gets accurate quotes
The brief structure that separates a project that can be estimated from one that cannot, with the eight sections worth writing before you talk to any developer.
ReadStrategyRebuild or repair: an honest test for an ageing website
How to tell whether your existing website needs a migration or a targeted fix, using five checks that take an afternoon rather than a month.
Read