You simply want to USE a database and not maintain it? Use Autonomous Transaction Processing!
Rating: 10 out of 10
Use Cases and Deployment Scope
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.
Pros
- One click deploy
- Self-maintaining
- Scalability of CPUs on demand on the fly
- Additional storage on demand on the fly
- Backups without interruption
Cons
- 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
Likelihood to Recommend
If your company's value is not increased by maintaining databases, you should use the ATP.
