Kemlat Header
Kemlat
  • Home
  • About
  • Services
    Business & TransformationA clear view of the problem and a plan you can deliver.8 Project & DeliveryGovernance that connects plans to results.3 ERP & CRMConnected processes and data in systems that fit your work.2 Digital ProductsWebsites, apps and platforms built around your needs.8 AI & AutomationPractical solutions for tasks that should take less time.8 Quality EngineeringMore confidence in every release.3 Cloud & SecurityA dependable foundation for your digital work.5 Managed ServicesStability, support and improvement after launch.3 Brand & CreativeAn identity and experience that tell your story clearly.4 Digital GrowthBetter visibility and decisions based on performance.5 Games & ImmersiveInteractive experiences for learning and for brands.4 Training & EnablementSkills your team can put to work.3
    All services56

    The KEMLAT Method

    KEMLAT
    Build your projectPick the services you need and get an approximate cost range in a minute.
  • Work
  • The Method
  • Insights
  • Contact
ARGet in touch
  • Home
  • About
  • Business & Transformation Project & Delivery ERP & CRM Digital Products AI & Automation Quality Engineering Cloud & Security Managed Services Brand & Creative Digital Growth Games & Immersive Training & EnablementAll services Build your project
  • Work
  • The Method
  • Insights
  • Contact
Get in touch
العربية [email protected] +962 79 122 3241
Check the Main Menu location in Apppearance->Menus->Display Location.
Choosing the Right Database and Hosting for a Business Platform - Kemlat Insights
Kemlat2026-10-21T16:50:47+03:00
All insightsاقرأ بالعربية
Enterprise Systems

Choosing the Right Database and Hosting for a Business Platform

The database and hosting decision is usually made in a five-minute developer conversation and lived with for ten years. What managers should ask before it is settled.

18 November 20265 min read
Share
Choosing the Right Database and Hosting for a Business Platform - Kemlat Insights

When a company commissions a custom platform, such as a customer portal or an internal operations app, the choice of database and hosting is often made quickly by whoever writes the code. It feels technical and slightly boring. Yet that choice decides how much the platform costs to run, how safe the data is, how easily it can grow, and how hard it will be to change vendor later.

You do not need to become a database engineer to take part in the decision. You need to understand a few trade-offs and ask the right questions.

Start with the shape of your data

Most business data is relational: customers have orders, orders have lines, lines refer to products, invoices refer to orders. The relationships matter, totals must add up, and two people should not be able to sell the last item at the same moment. For this kind of data, a relational database is the sensible default. PostgreSQL, MySQL and Microsoft SQL Server are the common choices, and all three are mature and widely supported.

Document databases such as MongoDB store records as flexible documents rather than fixed tables. They suit data whose structure varies a lot from record to record, like product catalogues with very different attributes or event logs. They can be a good fit for parts of a system, but they make reporting and strict consistency harder if your data is mostly a web of related business records.

For a typical mid-sized business platform, the practical guidance is simple. Use a relational database unless your developers can explain clearly, in business terms, why your data does not fit one. “It is faster to develop with” is not a sufficient reason on its own, because you will pay for it later when finance wants reports.

Skills and support matter more than benchmarks

Choosing between PostgreSQL, MySQL and SQL Server rarely comes down to performance for a mid-sized company. All of them handle far more than most business platforms will ever need. The better questions are about people and cost.

  • Who can support it? If your developer leaves, can you find another one locally who knows this database? PostgreSQL and MySQL skills are widely available, and SQL Server skills are common wherever companies run Microsoft systems.
  • What does it cost to license? PostgreSQL and the MySQL Community Edition are free to use. SQL Server has a free Express edition with size limits and paid editions beyond that.
  • What does it connect to? If your reporting runs on Power BI and your ERP (enterprise resource planning system) uses SQL Server, staying in that family may simplify integration. Most reporting tools connect well to all three.

Hosting options compared

Where the platform and database run is a separate decision. The main options look like this:

OptionSuitsWatch for
On-premise server in your officeStrict internal policies, existing server room and IT staffPower, cooling, hardware failures, backups and remote access all become your problem
Local data centre or hosting providerOrganisations that want data in-country with professional facilitiesCheck what is managed for you (backups, patching, monitoring) and what is not
Virtual server with a cloud providerTeams with technical skills who want flexibilityYou still patch, secure and back up the server yourself
Managed database and app services in the cloudMost new business platformsCosts grow with usage; region choice affects where data is stored

Managed database services from the major cloud providers handle patching, backups and failover (switching to a standby copy if the main database fails) for you. For a company without a dedicated database administrator, that is often worth more than the price difference. Several of the large providers now operate data centre regions in the Gulf, which can help with speed for users in the region and with organisational preferences about where data sits.

Data location is worth settling early. Some sectors have rules or regulator expectations about where certain data may be stored, and data protection laws in the region, including Jordan’s Personal Data Protection Law, include provisions on transferring personal data. Check your obligations with an adviser before you pick a region.

An illustrative scenario: a school network’s parent portal

Imagine a group of four private schools building a portal where parents see grades, attendance, fees and messages. The developer proposes a document database on a virtual server because that is what they used on their last project.

The school’s IT lead asks a few questions. Fees link to students, students to classes, classes to teachers and terms. Finance needs monthly reports on outstanding fees that must tie to the accounting system. The data includes children’s personal information. Nobody on staff can manage a server.

The answers point elsewhere: a relational database, run as a managed service in a region the school’s board has approved after taking advice, with automated daily backups and point-in-time recovery (restoring the data to any moment in the recent past, not only to last night’s backup), and the application on a managed app service. The monthly running cost is somewhat higher than a single virtual server, but the school no longer depends on one developer to keep the server patched and backed up.

Ask this question: “If the database were deleted by mistake at 2 p.m. today, what would we restore, from when, and how long would it take?” A clear, tested answer matters more than any feature list.

Questions to put to your developer or vendor

  1. Which database will you use, and why does it fit our data?
  2. Where exactly will the data be stored, and can we choose the country or region?
  3. How are backups taken, how long are they kept, and when was a restore last tested?
  4. Who applies security patches to the database and server, and how often?
  5. What will hosting cost per month now, and what happens to that cost if users or data double?
  6. If we change developer, what do we receive: source code, database access, documentation of the setup?
  7. Can we export all our data in a standard format at any time?

Ask for the answers in writing and keep them with the contract. They become the baseline for the operations runbook once the platform is live.

A foundation chosen on purpose

If your platform is already live, send the seven questions above to your developer this week and ask for a restore test within the month. If it is still being planned, make the written answers part of the contract, so the database and hosting choice fits your data, support capacity and budget rather than a developer’s habit. Making those choices deliberately, and documenting them, is part of the data architecture and platform development work in our Enterprise Systems service.

Found this useful?Share it with your team or someone who needs it.
  • WhatsApp
  • LinkedIn
  • X
  • Facebook
  • Telegram
  • Email
Related service

Enterprise Systems

We design and build systems, and migrate data into them, based on real operational needs, not generic templates.

Explore our services

Related insights

Single Sign-On and Identity: Keeping System Access Under Control - Kemlat Insights
Enterprise Systems

Single Sign-On and Identity: Keeping System Access Under Control

A sales manager leaves on Thursday and can still log in to the CRM five weeks later. Single sign-on and a clear identity process fix that,…

17 Nov 2026 · 6 min read
Cleaning Historical Data Before a System Migration - Kemlat Insights
Enterprise Systems

Cleaning Historical Data Before a System Migration

Moving fifteen years of records into a new system just in case is a frequent reason migrations run late. Decide what to bring, clean it properly…

16 Nov 2026 · 5 min read
Mobile Apps for Field Teams: When They Are Worth Building - Kemlat Insights
Enterprise Systems

Mobile Apps for Field Teams: When They Are Worth Building

Paper job sheets sent by WhatsApp make the case for an app feel obvious. Sometimes a custom app is right. Often a simpler option fits the…

15 Nov 2026 · 5 min read

Kemlat Footer
Kemlat
Kemlat

We help organisations transform complex operations into clearer ways of working, practical solutions, and measurable outcomes.

Quick Links

  • Home
  • About Kemlat
  • Our Services
  • Selected Work
  • The Method
  • Contact Us

Services

  • Business & Transformation
  • ERP & CRM
  • Digital Products
  • AI & Automation
  • Cloud & Security
  • Digital Growth
  • All services
  • Build your project

Get in Touch

Email [email protected]
Location Almadina Almunawwara St., Amman, Jordan
WhatsApp & Phone +962 79 122 3241

© 2026 Kemlat. All rights reserved.

Privacy Policy Terms of Use
Kemlat Method

Request a Service

Tell us what you need and we will get back to you within one business day.

By sending this form you agree to our privacy policy.

Request received

Thank you. Our team will review your request and contact you within one business day.