Skip to main content
Legia

Apps & Software

Choosing Technology for a Business Application: Considerations Beyond Developer Preference

The technology behind a business application determines maintenance costs and who can continue it years later. Here are six criteria management should weigh before the technology is decided.

SEO and Content Specialist

7 min read

Python code on a monitor screen

Short answer: choosing technology for a business application is best judged on six things you will carry after the project ends: availability of people who can continue it, the official support period of each component, licensing, the security update path, fit with where the application will run, and dependence on a single vendor. The technology your developers know best is not necessarily the lightest to maintain over the next five years, so the final decision deserves management involvement.

In the opening meetings of an application project, the choice of programming language, framework, and database is often left entirely to the developers. That is reasonable for technical detail. But operational applications are usually in use for years, and the technology choice determines who can maintain the system, when it must be upgraded, and what happens if the vendor no longer works with you. This article looks at choosing technology for a business application from the decision maker’s point of view, not at which framework is strongest.

Why technology choice is a management decision

Technology choice is a business decision because its effects appear long after the first developer has finished. The three most noticeable effects:

  • Maintenance cost. Every component has a support period. Once it ends, the application must be upgraded to a newer version, and a major upgrade can need its own budget.
  • Who can continue the work. If the technology is rarely used in the local labour market, finding a replacement developer or another vendor becomes harder and slower.
  • Your room to manoeuvre. Certain technologies tie you to one service provider or one licensing scheme that can change at any time.

Developers judge technology by how comfortable it is to build with. Management needs to judge it by the company’s ability to carry the system to the end of its useful life. Both are valid, and a good decision brings them together.

Illustration: web application

Six criteria for choosing technology for a business application

CriterionQuestion to askWarning sign
Availability of peopleHow easy is it to find other developers who know this technology in your city or country?Only one or two people on the vendor’s team know it
Support periodUntil when does the version in use receive bug and security fixes?The version in use is already, or nearly, out of support when the project starts
LicensingWhat is the license of each component, and what does it require if the application is used commercially?Components without a clear license, or per-user paid licenses not mentioned in the proposal
Security updatesHow are third-party library updates monitored and installed?No update plan after handover
Hosting fitCan the application run both in the cloud and on your own servers?It can only run on one specific provider’s service
Vendor dependenceCan another developer take over without the original vendor?The code is not handed over, or the documentation exists only in one person’s head

No technology passes all six criteria perfectly. The goal is to know which risks you are taking and to plan for them, not to find an option with no drawbacks.

Support period: how long the technology keeps getting fixes

The support period is the time during which a technology’s maintainers still release bug and security fixes for a given version. After that, newly found vulnerabilities are no longer patched for that version. Many large projects publish this policy openly, so you can check it yourself before approving a technology.

TechnologyOfficial support policyExample as of November 2026
Laravel (PHP framework)Each release gets bug fixes for 18 months and security fixes for 2 years; a major release comes out every yearLaravel 12 (released 24 February 2025): bug fixes until 13 August 2026, security fixes until 24 February 2027
PHPFull support for 2 years, then 2 years of critical security fixesPHP 8.2 receives security fixes until 31 December 2026
Node.jsLTS releases typically get critical bug fixes for a total of 30 months; production applications should only use Active LTS or Maintenance LTS releasesReleases in Current status are not recommended for production
PostgreSQL (database)Each major version is supported for 5 years from its initial releasePostgreSQL 14 is scheduled to get its final release on 12 November 2026

The examples above are not a ranking but a way to read support policies. The lesson for management: an application used for five years will almost certainly go through several major version upgrades of its framework, language, and database. Put those upgrades into the maintenance budget from the start, and make sure the project starts on a version with a long support period ahead of it.

Licensing and vendor dependence

A license is the set of rules for using a component, and those rules can change. On 10 August 2023, HashiCorp announced that future releases of its products would move from the Mozilla Public License 2.0 to the Business Source License 1.1. Companies already using its products had to reassess whether their use still complied. This example shows that license checking is not a one-off task at the start of a project.

Vendor dependence comes in two forms worth distinguishing:

  1. Dependence on a technology provider, for example a database or message queue service available only from one cloud provider. This is not always bad, but moving providers later means rewriting part of the application.
  2. Dependence on the vendor that builds the application, when the code, server access, or knowledge of the system is held only by the vendor. This second form is the one that most often harms companies, and the prevention lies in the contract. The clauses you need are covered in the article Source Code Ownership: Required Clauses in an Application Development Contract.

Ask the vendor to hand over a list of third-party components with their licenses. This list is also the basis for security monitoring.

Security updates and third-party components

Modern applications are largely built from libraries written by others, and every library can become a vulnerability. OWASP Top 10:2025 places software supply chain failures third, noting that the risk rises when the software in use is vulnerable, unsupported, or out of date. Its prevention advice is relevant to management:

  • Remove libraries, features, and files that are not used, to keep the attack surface smaller.
  • Check whether each library still receives security fixes. If not, plan a migration.

In practice, ask who monitors updates after the application is handed over, how often, and how it is paid for. An answer of “we’ll deal with it when there’s a problem” means there is no plan yet.

Availability of people and handover

Availability of people is the criterion most often forgotten, even though it does most to shape long-term cost. Global surveys such as the Stack Overflow Developer Survey give a picture of which technologies developers use widely, but the labour market in your city can differ. A simple way to test it: search local job portals for openings and developer profiles for that technology, then compare the numbers with the alternatives.

Handover covers this risk from the other side. Even a common technology is hard to continue without documentation, architecture notes, and instructions for running the system on a new developer’s computer. Put documentation requirements into the requirements document from the start, so they are included in the proposal.

Questions for the vendor before the technology is decided

  1. Which technology is proposed for the application, the database, and its deployment, and why for our case?
  2. Until when is the version in use supported, and when does the next major upgrade need to be budgeted?
  3. What is the license of each component, and are there recurring license fees?
  4. Can the application run on our own servers if we ever move away from the cloud, or the other way round?
  5. How are library security updates monitored after handover?
  6. Where is the code stored during the project, and what documentation is handed over?
  7. If we change vendors, what will a new developer need to continue?

How Legia does it

On its Web Application Development service page, Legia openly lists the technology it uses: Laravel, Node.js, React, and TypeScript for the application, PostgreSQL and Redis for data, and Docker for deployment. The application can be deployed on cloud infrastructure or on your own servers, and the deployment option is discussed during the requirements mapping stage. The source code and its usage rights belong to you, stored in a repository under your company’s name from day one, along with technical documentation so other developers can continue without depending on Legia. After the 30-day fix period following handover, a subscription maintenance plan is available, or your internal team can take over. Other services in this pillar are on the Applications & Software page.

Frequently asked questions

Does the company need to specify the technology in the requirements document?

Not necessarily. What matters more is stating the constraints: where the application will run, the company’s licensing policy, and the technology the internal team already knows. The vendor then proposes the technology with reasons you can assess.

What if an old application uses a version that is already out of support?

The application keeps running, but new vulnerabilities are no longer patched for that version. Draw up a phased upgrade plan, starting with the components that face the internet.

Is the most popular technology always the safest choice?

Not always. Popularity makes it easier to find people, but the version’s support period, licensing, and fit with your needs still have to be checked one by one.

Who should decide on the technology on the company’s side?

Ideally one person who understands the business, supported by someone who understands the technical side, such as an internal IT manager or an independent consultant. The vendor’s developers propose, the company decides.

Sources

Category Apps & Software

Keep reading

Related articles

All Articles