MacBook-Pro:~ javiermugueta$ oci session authenticate
Enter a region (e.g. ca-toronto-1, eu-frankfurt-1, uk-london-1, us-ashburn-1, us-gov-ashburn-1, us-gov-chicago-1, us-gov-phoenix-1, us-langley-1, us-luke-1, us-phoenix-1): eu-frankfurt-1
Please switch to newly opened browser window to log in!
Completed browser authentication process!
Enter the name of the profile you would like to create: tef
Config written to: /Users/javiermugueta/.oci/config
Try out your newly created session credentials with the following example command:
oci iam region list --config-file /Users/javiermugueta/.oci/config --profile tef --auth security_token
MacBook-Pro:~ javiermugueta$ oci session validate --profile tef --auth security_token
Session is valid until 2019-04-08 22:56:48
But not only is easy to use and maintain because you don’t have to deal with administration tasks or manage different technologies for persisting data, in fact you have a very easy mechanism for versioning your microservices in parallel with your data: just by cloning the instance.
You can clone both with the dashboard or with commands that can be easily put in your CD pipeline.
oci db autonomous-database create-from-clone --compartment-id <mycompid> --cpu-core-count 1 --data-storage-size-in-tbs 5 --admin-password <password> --source-id <dbsourceid> --clone-type FULL --db-name <newname>
As an example, in the range of a 4-5 minutes you can clon a 5TB database ready to be connected to a new version of your microservice.
With Oracle Autonomous Database you avoid the versioning anti-pattern quickly and easily.
And what about putting an API Platform in between the users and the microservices? Think about it!