Databricks Lakehouse Platform vs. Oracle Exadata

If you need a managed big data megastore, which has native integration with highly optimized Apache Spark Engine and native integration with MLflow, go for Databricks Lakehouse Platform. The Databricks Lakehouse Platform is a breeze to use and analytics capabilities are supported out of the box. You will find it a bit difficult to manage code in notebooks but you will get used to it soon.

Incentivized

• First, get the database on Oracle. If you are in an Oracle stack, it would be much better to use the Oracle products. If you are driving a Ferrari, you wouldn’t put a Mercedes engine in it. If you are writing a query, you cannot rely on other brands. Since I'm an architect, when I look for a product, I look for performance.
• The installation is easy because it comes out-of-the-box and you just start using it.
• Previous to Oracle Exadata, we were using a normal Oracle RAC service. We were just waiting for this product to come out.
• I'm currently writing a data warehouse on Exadata. Before this solution, we were aiming for this to be completed by 8 a.m., when our ETLs would finish. With the help of Exadata's special features, this was reduced to 3 a.m. This solution allows us to bring more data within the same time period. It provides us with more subject areas that provide more reports to our users. Our ETL times reduced to 65%, then to 50%.

Incentivized

• Process raw data in One Lake (S3) env to relational tables and views
• Share notebooks with our business analysts so that they can use the queries and generate value out of the data
• Try out PySpark and Spark SQL queries on raw data before using them in our Spark jobs
• Modern day ETL operations made easy using Databricks. Provide access mechanism for different set of customers

Incentivized

• Customize-able for specific functionality optimized for combination of online transaction or analytical processing.
• Ability to serve mix workloads with resource management feature enables prioritizing allocation for certain workload.
• Scale-able on-premise with compatibility for cloud deployment offers flexible solution for organization considering to transition from on-premise solution.

Incentivized

• Connect my local code in Visual code to my Databricks Lakehouse Platform cluster so I can run the code on the cluster. The old databricks-connect approach has many bugs and is hard to set up. The new Databricks Lakehouse Platform extension on Visual Code, doesn't allow the developers to debug their code line by line (only we can run the code).
• Maybe have a specific Databricks Lakehouse Platform IDE that can be used by Databricks Lakehouse Platform users to develop locally.
• Visualization in MLFLOW experiment can be enhanced

Incentivized

• Patching can often become quite involved and convoluted. It should be more transparent and straightforward.
• Storage metrics can be difficult and time consuming to obtain.
• Basic administrative functions can be hard to repair when discovered.
• Vendor support can take a while to obtain. Generally several attempts are necessary to reach the right area of vendor expertise.

Incentivized

Because it is an amazing platform for designing experiments and delivering a deep dive analysis that requires execution of highly complex queries, as well as it allows to share the information and insights across the company with their shared workspaces, while keeping it secured.

in terms of graph generation and interaction it could improve their UI and UX

Incentivized

One of the best customer and technology support that I have ever experienced in my career. You pay for what you get and you get the Rolls Royce. It reminds me of the customer support of SAS in the 2000s when the tools were reaching some limits and their engineer wanted to know more about what we were doing, long before "data science" was even a name. Databricks truly embraces the partnership with their customer and help them on any given challenge.

Compared to Synapse & Snowflake, Databricks provides a much better development experience, and deeper configuration capabilities. It works out-of-the-box but still allows you intricate customisation of the environment. I find Databricks very flexible and resilient at the same time while Synapse and Snowflake feel more limited in terms of configuration and connectivity to external tools.

Oracle Exadata Database Machine had the best performance overall hands down. It clearly beat the competition and we were seeing 1000X improvement on SAP HANA. Oracle Exadata Database Machine beat that without us refactoring our code. To achieve that in HANA, we had to refactor the code somewhat. Now this was for our limited POC of 5 use cases. Given the large number of stored procedures we had in Sybase, we need to capture more production metrics but we are seeing incredible performance.

Incentivized

• The ability to spin up a BIG Data platform with little infrastructure overhead allows us to focus on business value not admin
• DB has the ability to terminate/time out instances which helps manage cost.
• The ability to quickly access typical hard to build data scenarios easily is a strength.

Incentivized

• Single support from a single vendor with both machine and database from Oracle, which is costing us less.
• With Exadata, we need less technical manpower and less technical support. A business transaction with the integrated and centralized database helps us focus on other business needs.
• We don't need to buy additional licenses and Hardware for the next 3 to 5 years.

Incentivized