Oracle Backend with Firebase APIs bridges mobile dev and enterprise databases via ORDS

·2 views

Oracle Backend with Firebase APIs is a free feature of Oracle REST Data Services (ORDS) that allows mobile and web developers to build apps directly on top of Oracle AI Database using familiar Firebase-style SDKs for iOS, Android, Flutter, and JavaScript. The feature exposes authentication, document storage, file storage, security rules, and AI vector search through those SDKs without requiring app clients to hold direct database connections. Instead, all requests travel over HTTPS to ORDS, which maintains its own JDBC connection pool and routes calls to server-side PL/SQL packages running inside the database schema. This architecture keeps database credentials and hostnames entirely hidden from client apps, while allowing enterprise Oracle estates to serve mobile teams that would otherwise rely on separate services like Firebase or Supabase. The setup effectively closes a long-standing gap between governed Oracle database environments and the backend-as-a-service tools typically favored by app development teams.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Opinion: Nerd Culture Seen as Threat to Intellectual Discourse

An opinion piece published on The Intrinsic Perspective argues that nerd culture is having a damaging effect on intellectualism. The article suggests a tension between mainstream nerd identity and deeper intellectual engagement. The piece was shared on Hacker News, where it received minimal traction with only 3 points and no comments. The full argument and supporting details are available via the original publication link.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

A developer found 4 of 9 deployed pages were 404 despite a 'success' message

A developer discovered that four of nine newly deployed pages returned 404 errors shortly after a deployment tool reported a successful upload. Checking the live URLs directly revealed the issue was edge propagation, and all pages resolved to 200 within seconds — but only because the developer verified manually. The incident highlighted a broader pattern: tools like deploy CLIs, task schedulers, and shell pipelines truthfully answer a narrow question, but that answer is often misread as confirmation of a wider outcome. The author also found that a shell pipeline was silently masking a non-zero exit code from a guarded script, because the pipe reports the last command's status rather than the whole chain. The core lesson is that a success report only testifies within its own jurisdiction — not whether the intended end result was actually achieved.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Six Hard Questions Enterprises Must Now Answer in the Age of Agentic AI

At KPMG's annual Tech and Innovation Symposium, six foundational questions emerged that enterprises are grappling with as AI shifts from an assistive tool to one that autonomously performs work. KPMG's Steve Chase warned that bolting AI onto existing processes — workable in the assisted-AI era — becomes far more costly and risky as agentic AI takes hold. Companies are now being pushed to think in terms of multi-model architectures, cost visibility at the token level, and deliberate workforce reskilling rather than relying on training videos alone. The consensus was that AI adoption requires genuine organizational redesign, with early adopters pairing directly with business units to spread practical knowledge. Beyond internal transformation, firms are also beginning to rethink external business models, including shifting from input-based to outcomes-based pricing and reconsidering what their core products even mean in an agent-driven world.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Rebuilds TravelAI.Core as Multi-Service Architecture with RabbitMQ

A developer is overhauling TravelAI.Core, a .NET library for AI-powered travel destination search, from a single-package library into a distributed multi-service system. The upgrade splits the codebase into three independent services — API, Search, and AI — each handling a distinct responsibility to allow independent scaling. RabbitMQ will be introduced as a message queue between services so that slow or unavailable AI providers do not block the entire application. Centralized logging via Serilog will replace scattered console outputs across services, making it easier to trace failures in a multi-service environment. The entire system is designed to run locally via Docker, serving as a practical, open-source reference for building resilient production-grade architectures.

0 comments Read more at DEV Community