Last updated: · Prepared by DataKobi Engineering Team
Database Services
DBaaS (Database as a Service) means an expert DBA team takes over installation, backup, updates and performance management of your databases as a service. PostgreSQL, SQL Server, Oracle and MySQL are supported.
The database is the heart of your application and the source of most outages. Hiring a good DBA is both hard and expensive; round-the-clock on-call coverage takes at least two people. With DataKobi DBaaS, your environments are our responsibility, with high availability, automatic backups and continuous performance monitoring.
Slow queries? Our monitoring layer catches the slowdown before you notice it, and our DBA team comes with index and query plan recommendations. Version upgrades are rehearsed in a test environment and applied in a maintenance window — so you don't end up five versions behind out of 'if it works, don't touch it' fear.
Key features
High availability
A second copy via streaming replication / AlwaysOn; automatic failover.
Point-in-time recovery
PITR: roll the database back to any second you choose.
Performance clinic
Slow query analysis, index recommendations, capacity planning report.
24/7 DBA on call
When replication breaks at 3 AM, we are the ones who wake up, not you.
Is migrating from Oracle to PostgreSQL really possible?
For most workloads, yes — and the motivation is strong: Oracle's per-core licensing costs have typically translated into savings of over 70% for customers who moved to PostgreSQL. The process is disciplined: first a compatibility analysis (an ora2pg report) measures how much of your PL/SQL code will convert automatically; 80-90% automatic conversion is common, and the remaining packages are rewritten by hand. Data migration is synchronized live with CDC (change data capture); application testing is completed while the two systems run in parallel, and the final cutover takes place in a short window. There are exceptions that cannot be migrated — packaged software deeply dependent on Oracle (some ERPs) is identified during the analysis, and we tell you so honestly.
How is database high availability designed?
There is no single correct architecture; the RPO/RTO target and the budget decide. On PostgreSQL, a synchronous second copy via streaming replication provides near-zero data loss, and automatic failover with Patroni takes under 30 seconds. On SQL Server, an AlwaysOn Availability Group serves the same function; on Oracle, Data Guard is used. The critical question is usually skipped: is the failover itself tested? At DataKobi a failover drill is held every three months, and it is demonstrated that the application connects to the new primary automatically. PITR (point-in-time recovery) is also standard in every package: in the 'we dropped the wrong table at 14:32 yesterday' scenario, the database is rolled back to that exact second.
Technical Specifications
- Engines: PostgreSQL, SQL Server, Oracle, MySQL/MariaDB, Redis
- Backup: Daily full + continuous WAL/log; up to 35 days of PITR
- Security: Encrypted connections (TLS), at-rest encryption, masking
- Monitoring: Dashboard for query time, locks, replication lag
- SLA: Starting at 99.95%, 99.99% for clustered setups
Frequently Asked Questions
How can I get rid of Oracle license costs?
My database keeps growing and the disk is always full. What's the solution?
Will the application's connection details change?
A 30-minute discovery call with your architect
We will listen to your needs and outline the right architecture and a clear pricing framework in the same call. The first consultation is free.