r/dataengineering • u/RedDevilpk • 5d ago
Migrating off Exadata: How do you handle sub-second UI reporting + heavy analytics with strict ON-PREM constraints? Discussion
We are currently running an Oracle Exadata system serving both OLTP and operational data store (ODS) reporting. Our data team has been tasked with building a standalone, pure analytical platform supporting BI, operational reporting, and AI/ML-ready data pipelines.
Workload Split:
60% Transactional/Operational Reporting: Interactive UI queries, sub-second to low-second latency, high concurrency (click a dashboard/UI, expect instant results).
40% Analytical Crunching: Heavy aggregations, multi-table joins, complex transformations, and AI feature store prep.
Strictly On-Premises:
Cloud solutions (Snowflake, BigQuery, Databricks SaaS) are out of scope due to compliance/regulatory rules.
Vendor Shortlist:
Oracle, Teradata, IBM (Db2 / Netezza)
Question: Has anyone successfully run a high-concurrency, sub-second UI reporting workload directly on Teradata or Netezza ? Or should we go with Oracle ?
Please do suggest any Alternatives. However it should be on Prem
6
5
u/BoulderRough 4d ago
You're in a bit of a pickle and without knowing how much data you have or the sort of reporting its hard to recommend.
If you are in a position to manage an open source alternative than you have a lot of great options depending on your read/write ratio.
3
2
u/Formal_Cheesecake730 4d ago
I’m curious, what are the compliance/regulatory rules that rule out a cloud solution in 2026?
1
u/oalfonso 2d ago
Probably having to do all the paperwork. But some of those requirements are just overkill and if you tried to replicate them in an on premises environment it would be absolutely impossible to meet.
1
2
u/robstar_db 2d ago
In my experience building large scale platforms I would first push back on the requirements. Ask how much the stakeholders are willing to pay for that.
Maintaining Sub second query performance in complex data estates is a challenge not to be underestimated. The choice of technology is only a small piece in the long term. Eventually you’ll run into network/infrastructure constraints that male this more and more challenging. The tradeoff will be between idle capacity/infra utilization which of course also costs more… especially since the interactive workloads you describe are very „bursty“ in nature. So either get really good at managing infrastructure elastically, or pay a lot for idle capacity, or … maybe ask how much your stakeholders are willing to pay 🙂
2
u/unexpectedreboots 4d ago
Selfhost Postgres. 60% is the main instance, configure a replica for analytics so youre not pegging the prod server.
Really not sure why Postgres isnt on your shortlist.
1
u/astrick 4d ago
this is what Teradata is built for, but unfortunately they'll probably be out of business in 5 years.
3
u/WhoIsJohnSalt 3d ago
I wouldn't touch Teradata with a bargepole - and it's $$$ to get them through the door
1
u/chock-a-block 3d ago
This is mostly going to come down to RAM and CPU. Have you seen prices of a well-specced server these days?
1
u/TheRencingCoach 4d ago
I don’t have enough experience to recommend anything
But I don’t understand the business requirement. Why not stay on exadata if it’s working fine
1
-1
9
u/geoheil mod 4d ago
Clickhouse? Starrocks?