Overall Satisfaction with Oracle Autonomous Transaction Processing
We use the Oracle Autonomous Transaction Processing to handle all our data for our underlying microservice architecture. A decision for the architecture was not to maintain a single database per service, but have one database handle all data across all services. The database required an easy scalability possibility and as there were not DevOps hired to maintain databases, it must be a fully self-maintaining out of the box solution - hence: autonomous. The Oracle Autonomous Transaction Processing spins up in less than 5 minutes, is scalable on-demand, runs backups on the fly and does all updates automatically without interruption.
- One click deploy
- Self-maintaining
- Scalability of CPUs on demand on the fly
- Additional storage on demand on the fly
- Backups without interruption
- Connectivity between ATP and Oracle Kuberentes Engine cluster seems to drop randomly
- The ATP could come in an even smaller shape as the smallest shape is already quite big . But if must be more than always free, as that version does have connectivity limitations about 20 connections
- Approx 100 times faster spin up than manual setup of an Oracle DB
- 3h annual maintenance for big version releases (18c to 19c) compared to est. 500h annual maintenance with manual database updates