{ Abhilash Kumar Bhattaram : Follow on LinkedIn }
I spend my days on the infrastructure side of things — migrations, capacity planning, licensing conversations, moving workloads onto Oracle Autonomous AI Database and OCI.
I don't write mobile apps. I've never shipped an Android build or wrestled with an Xcode provisioning profile.
So when I first heard about Oracle Backend with Firebase APIs, my honest first reaction was: "that's a developer thing, not my thing , but I relaized a DBA needs to understand ORDS
A few days in, I've had to look into it as my Dev Team asked for some support on this Once our data is on Oracle AI Database, what else can we do with it?" Usually that means analytics, or AI workloads, or vector search for RAG. It almost never means "can our mobile app team build directly on top of this too" — because historically, the honest answer was no. Mobile and web teams reach for Firebase, Supabase, or some other backend-as-a-service, and the database team's carefully governed, audited, encrypted Oracle estate sits in a completely separate world from the app.
