Great database, but crucial options have its cost
October 24, 2017
Great database, but crucial options have its cost
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Oracle Database
Oracle Database is being used as a backend into a custom Distribution Management System (DMS) and Outage Management System (OMS), including modules for outage, voltage variation, fraudulent consumption, among others.
- Clustering with Real Application Clusters (RAC)
- External data access with External Tables
- XML navigation and parsing with XMLDB
- Object creation with user defined types (UDT)
- Cost of important options (as Parallel Query, Partitioning, AWR, etc.)
- Cost of licensing
- Lack of DevOps features support
- On premises solutions requires a high upfront investment (CAPEX and OPEX).
- In opposite way, cloud solutions require a lower upfront investment, but some part of CAPEX is moved to OPEX (management, availability, support, etc.).
- As any other RDBMS, Oracle Database requires that the application development team (Java, .NET, etc.) has knowledge regarding SQL database architecture, otherwise, a lot of rework will be needed in the future, which to me is a major reason to unscalable applications with high demand.
The database selection was not my decision, but i think that under heavy load, Oracle outperforms these alternatives when you put only performance on the table. When a cost-effectiveness analysis is done, depending of your level of demand, some of these competidors can have space into your solution, but you can need to use architectures like server clustering para support the demand