Insights
Insights · FAQ
Questions we hear most when teams adopt and run open-source databases, plus criteria to help choose an engine.
Guide
Which database should you choose?
The right answer depends on your workload and team. Here is a common starting point.
| Engine | Strengths | Good fit | Considerations |
|---|---|---|---|
| PostgreSQL | Standard SQL, rich types and extensions (JSONB, GIS …), strong optimiser | Complex business systems, mixed analytics, commercial-DB replacement | Engine-specific concepts such as VACUUM and connection management |
| MySQL | Huge ecosystem, simple operations, easy read scaling | Web, commerce, OLTP, managed cloud | Understand the LTS/Innovation release cadence |
| MariaDB | Galera synchronous clustering, multiple storage engines | MySQL compatibility + multi-primary HA | Growing compatibility gap with MySQL |
| InfluxDB | Optimised time-series writes and aggregation, retention policies | Monitoring, IoT, equipment metrics | Big 2.x vs 3.x differences; cardinality design |
Checklist
Ten pre-production checks
- RPO/RTO are written down
- You have actually restored from a backup
- You have rehearsed failover
- Monitoring and alert recipients are defined
- Top queries are reviewed regularly
- You know your disk growth trend
- Accounts are least-privilege by role
- Traffic is encrypted with TLS
- You know your version’s end-of-support date
- Every change has a rollback plan
Lifecycle
Version lifecycle notes (October 2026)
| Engine | Status | Recommendation |
|---|---|---|
| PostgreSQL | Supported: 18·17·16·15·14 / 14 ends 2026-11-12 / 19 at RC stage | Plan upgrades if on 14 or older |
| MySQL | 8.0 EOL April 2026 (Sustaining Support) / 8.4 LTS and 9.7 LTS available | Move 8.0 → 8.4 LTS |
| MariaDB | LTS: 10.11·11.4·11.8·12.3 / 10.6 community maintenance ended July 2026 | Upgrade to an LTS if on 10.6 or older |
| InfluxDB | 3 Core/Enterprise 3.x in active development; 2.x OSS maintained | Evaluate 3.x for new builds; plan migration for 2.x |
| Cloud managed databases | Azure Database for MariaDB retired 2025-09-19 / NCP offers no managed MariaDB / managed engine versions follow each cloud’s support calendar | Feed managed-service engine end-of-support notices into upgrade plans |
FAQ
Frequently asked questions
Are open-source databases stable enough for enterprise use?
Yes. But HA, backup and monitoring that commercial databases bundle must be assembled from open-source tools, so design and operating procedures determine stability.
Who provides support without a vendor?
Community editions have no vendor contract, so an in-house team or a specialist maintenance provider fills that role. OpenDB Works does so within the contracted scope.
Can we order just a diagnosis?
Yes. With read-only access we collect configuration, metrics and logs and deliver a report with risks and improvement priorities.
Is our data safe during the work?
Work happens only through agreed accounts, paths and windows; customer data is never taken out or used beyond the purpose of the work. We follow your security policies and agreements.
What information speeds up a consultation?
Database type and version, server specs and count, data size, HA topology, the current problem (symptoms and timing) and your preferred schedule.
Managed cloud database or self-managed?
Managed services take over backup, patching and HA and reduce operating effort; self-managed gives freedom over extensions, parameters and versions. We compare needed extensions, cost and staffing.
Who owns the cloud accounts under an MSP contract?
Typically you own the accounts and data, and OpenDB Works operates with delegated permissions. Permission scope and revocation are documented in the contract.
How long does Oracle → cloud PostgreSQL take?
It varies widely with object count, PL/SQL volume, data size and downtime target. We estimate the schedule from assessment reports and rehearsal results.
Shall we start by reviewing your cloud and databases as they are today?
Tell us your clouds, database versions, topology and concerns, and we will propose an assessment scope and approach.