Comparison with Self-built Databases
| Comparison Item | UDB-MySQL | UHost Self-built | Self-built Database |
| Cost Performance | Elastic Resources | Elastic Resources | Large sunk cost for one-time investment |
| Kernel tuning to improve performance | No performance optimization for open source version | No performance optimization for open source version | |
| Free backup space | Need to purchase resources for backup space | Need to separately prepare backup resources, with extremely high costs | |
| Availability | High-availability version provides dual-master hot backup architecture, achieving about 20-seconds failure recovery | Need to purchase a high-availability system separately | Need to purchase a high-availability system separately |
| Cloud platform enables read-write separation with one click to achieve load balancing, convenient to use | Need to implement load balancing separately | Need to implement load balancing equipment separately | |
| Reliability | High data reliability, supports physical backup and logical backup, backup recovery, and seconds-level rollback, etc. | High reliability can be achieved under good architecture | Average data reliability, depending on the damage probability of single disk |
| Ease of Use | Automated backup recovery system, supports point-in-time recovery, etc. | No automatic backup system, the implementation of streaming backup capability and point-in-time recovery function are costly | No automatic backup system, the implementation of streaming backup capability and point-in-time recovery function are costly |
| Automated monitoring alarm system, supports second-level monitoring, covers all performance indicators of instances and databases, supports SMS, email, etc. | Need to separately purchase a monitoring system and set up alarm system in cloud monitoring | Need to separately purchase or set up a monitoring system, fewer channels available, with higher cost | |
| Supports cross-availability zone disaster recovery | Implementation is technically difficult | Establishing cross-availability zone data centers is extremely costly, technically challenging, making it difficult to achieve cross-availability zone disaster recovery | |
| Performance | NVMe-model MySQL delivers superior performance, extremely cost-effective | Local disks equals to lower data reliability, if adopting cloud disks, architecture planning is needed and the costs are higher | Generally lower than cloud database in performance as hardware update speed is slower than cloud computing |
| Performance is robust and load balanced after adding read-only instances | It's challenging to implement master+slave architecture, resulting in high consulting cost and maintenance cost | It's challenging to implement master+slave architecture, resulting in high consulting cost and maintenance cost | |
| Provides a wealth of monitoring indicators, meeting most monitoring and performance optimization database scenarios | Relies on senior DBAs, which is expensive and restricted people | Relies on senior DBAs, which is expensive and restricted people | |
| Security | Intranet isolation controls access, VPC network isolation | VPC network isolation | Network isolation consulting cost is high |
| Supports database auditing | Auditing is difficult, need to save SQL logs separately | Auditing is difficult, need to save SQL logs separately |
