Day 11 - 30 Days on the Oracle Cloud
It took a little longer than I had hoped to publish the next article in this series about my experience with a 30-day Oracle Cloud trial. I had a created compute instance in the same compartment and that messed up my estimates. That's just one piece of the puzzle.
The other shocking observation was that hosting the database was terribly cheap and we're talking about Oracle pricing.
The Database Cloud Service is available on the Oracle Cloud Infrastructure (OCI) and featured as an easy to deploy and configure database system. They are available as a Virtual Machine (VM), Bare Metal servers or on state-of-the-art Exadata hardware. Customers can either provision them with the database license included or BYOL (Bring Your Own License). You can get the latest pricing for this service here.
In the case of the trial account, it appears that I am only being "billed" for the cost of resources needed to run a DB System:
- CA$0.086 per OCPU hour - this is the price for a VM.Standard2.1 VM that comes with 1 OCPU and 15 GB memory.
- CA$0.0573 for 1 GB per month of Block Storage - usage for the day was 22.97 GB that totals to approximately 712 GB per month. This is the smallest capacity that can be provisioned for a DB system, of which, 256 GB is for user data.
- CA$0.0343842 for 1 GB per month of Object Storage - I had performed only one full backup. For the trial it seems impossible to enable automatic daily backups that would been useful to have a better sense of true costs. The usage for a backup without creating any data was 0.02 GB. That amounts to approximately 0.62 GB for the month. I did not do any recovery or anything that might have been considered a "request", so no charges were incurred there.
In the absence of an actual charge on using a fully-licensed Standard Edition database, I am forced to rely on how much it would cost to host the DB System through their web pricing, which is CA$0.5437 per OCPU hour. Using the Cost Estimator, that amounts to about CA$404.51 per month. Unless someone tells me otherwise, I will also assume that one would need to budget for the minimum 712 GB Block Storage and any Object Storage usage. They aren't terribly expensive, but it's good to have that buffer and not be surprised at the end of the pay period.
In the case of using Object Storage for RMAN backups, it would be worth noting that in the Cost Estimator, the Oracle Database Backup Cloud Service is available and can be added to the configuration. It costs more than the "regular" Object Storage charges but according to the pricing calculator, has unlimited inbound data transfer and DELETE requests. There will likely be other charges (outbound data transfers and requests) should recovery be needed or creating a new DB System from the backups.
While pay-per-use models might seem to be a fairer way of charging customers, it does add a huge layer of complexity when estimating costs. For that reason, it's no wonder why developers find the OCI (or even Amazon Web Services) "hard" and prefer more budgeting-friendly cloud providers like DigitalOcean and Linode.
That being said, none of these developer-friendly platforms provides Oracle Database Standard Edition and up. Spending about CA$4,848 annually would almost seem reasonable compared to hosting on-premise considering the cost of:
- Hardware - servers, network, power and redundancy equipment
- Software licenses
- Physical space to house the equipment
- Other systems and equipment needed to ensure uptime and security
- Specialists for maintaining equipment, network and systems
Probably the only non-subscription cost that is needed is for hiring a qualified expert, the OCI Administrator!