A non-technical guide to the decisions behind a business application's technology stack — and the questions that matter more than trends.
When you commission a business application — an internal system, a customer portal, a mobile app — you'll hear about its 'stack': the languages, frameworks, databases and hosting it's built on. These choices are technical, but their consequences are business ones: cost, speed of delivery, reliability and how easy it will be to find people to maintain the software in future.
You don't need to be an engineer to ask the right questions. Here is a practical way to think about it.
Start from the problem, not the technology
The right stack depends on what the application must do. Before any technology is discussed, it helps to be clear about:
- Who will use it — customers, staff, partners — and on which devices.
- How many users and how much data you expect in the next few years.
- Which existing systems it must connect to.
- Whether it must work offline or in low-connectivity environments.
- Any regulatory, data-location or security requirements.
The main layers of a stack
Frontend: what users see
For web applications, React-based frameworks such as Next.js are a widely used, well-supported choice. For mobile, cross-platform tools such as React Native let one codebase serve both Android and iOS. Using the same language across web and mobile — typically TypeScript — reduces duplication.
Backend: the business logic
The backend enforces rules, processes data and connects to other systems. Node.js with a structured framework like NestJS is a common choice that shares TypeScript with the frontend. The most important qualities are clarity of structure and testability, not novelty.
Database: where data lives
Business data with relationships — customers, orders, invoices, stock — usually belongs in a relational database such as PostgreSQL, which protects consistency. Document databases such as MongoDB suit flexible or rapidly changing data structures. Many systems use one primary database and add others only for specific needs.
Hosting and deployment
Managed platforms reduce the operational work of running servers. What matters is reliability, backups, monitoring, and that accounts are owned by your company.
Five questions that matter more than trends
- Is it mature and widely used? Popular, well-documented technologies are easier to maintain and hire for.
- Does it fit the team? A stack your developers know well will be built faster and with fewer mistakes.
- Is it appropriately simple? Fewer moving parts mean fewer things to break. Complexity should be justified by a real requirement.
- Can it integrate? Check that it works well with the payment, accounting, messaging or ERP systems you rely on.
- What is the long-term cost? Consider hosting, licences and maintenance over several years, not just the initial build.
Red flags
- A technology chosen mainly because it is new or fashionable.
- An architecture far more complex than the problem — for example, many separate services for a small internal tool.
- Proprietary platforms that make it difficult to move your data or code later.
- No clear plan for backups, monitoring and security updates.