Urgent.News

What's breaking now, across hundreds of outlets.

Tech

How BabySea built adaptive provider selection on Databricks

BabySea is the execution control plane for generative media: one API across 80+ image and video models from 12+ AI labs, served by 8+ inference providers, running in three sovereign regions: US, EU, and APAC. The hard problem is not exposing models. The hard problem is execution: deciding, per request, which provider should actually run a given model in a given region under real latency,…

BabySea, an execution control plane for generative media, offers one API across 80+ image and video models from 12+ AI labs, served by 8+ inference providers in three sovereign regions: US, EU, and APAC. The critical challenge lies not in exposing models, but in executing them optimally based on real-time latency, reliability, and cost conditions. To address this, BabySea utilizes Databricks, an intelligence layer that enables adaptive provider selection instead of static routing.

Customer executions generate attempt records, which first land in regional Supabase systems due to Postgres serving as the operational source of truth for the product. Databricks integrates directly with this data stream to form a continuous learning loop. The critical architectural decision is avoiding a separate analytics estate, instead embedding Databricks within the control loop to improve execution outcomes while maintaining operational safety.

A common pitfall in "smart routing" systems is making the intelligence plane a dependency for serving traffic, leading to degradation when the ranking service fails. BabySea's design ensures Databricks computes rankings while the API consumes a cached export of that ranking, always retaining deterministic fallback behavior if Databricks or cache infrastructure fail. This design treats adaptive selection as an enhancement, never a dependency.

The runtime chain begins with customer traffic producing provider-attempt telemetry in regional Supabase. Databricks reads this telemetry and transforms it into provider-performance and provider-ranking artifacts, exporting these rankings to Upstash. The API reads the exported ranking for generation_provider_order, prioritizing "fastest" configuration while circuit-breaker logic and failover mechanisms remain in place. Later customer traffic feeds new telemetry, continuously improving the system.

When a customer requests "fastest," the API reads one Upstash Redis-protocol key, filters this ranking against providers configured for the requested model, and moves on. This hot path does not include Databricks SDK calls, MLflow clients, or Mosaic AI Model Serving fetches. All Databricks operations occur upstream of this line, ensuring the hot path is swift and efficient.

BabySea's data strategy avoids copying operational data unless it's critical. Using Unity Catalog Lakehouse Federation, each regional Databricks workspace connects to its matching regional Supabase database via a PostgreSQL foreign connection. This approach provides a governed entry point into operational routing telemetry without introducing additional ETL systems or consistency problems.

Data columns carry governed tags like gdpr_status, tenant_boundary, and ai_telemetry, ensuring the routing system reads multi-tenant, region-sensitive execution data that feeds training, ranking, analytics, and operational validation.

Refining the data through a Lakeflow Spark Declarative Pipeline into a Bronze, Silver, Gold medallion on Delta Lake forms the core of BabySea's routing intelligence. Bronze lands federated operational tables into Delta-backed materialized views, isolating the product database from downstream transformations and establishing a Delta-native substrate for analytics, training, and export.

Silver enriches provider attempts with routing-relevant fields and prepares data for ranking. Gold finalizes the ranking data for API consumption. This Medallion design ensures accurate, efficient, and governed routing intelligence, distinguishing BabySea's approach from generic analytics solutions.

Rewritten by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

SMS OTP API Template Ownership for SaaS Login Verification (With Auditable Email Handoffs)

Option Pick this when Template ownership decision Twilio Verify A dedicated verification product is your starting point. Evaluate its verification template controls against your signup wording and…

  • Email verification links are trust proofs, while SMS codes are possession proofs.
  • For B2B SaaS signup, keep ownership of email verification-link template explicit.
  • Use managed SMS OTP when a code is required for user verification.

Conflict Lab: Customer Service Readiness Assessment Powered by Presage SmartSpectra

This is a submission for the Presage SmartSpectra SDK Challenge . What I Built How do you know if a customer-service employee is ready to handle an angry or confrontational customer before they face…

  • Conflict Lab uses Presage SmartSpectra for customer-service readiness assessment
  • Application evaluates facial presentation and spoken responses via AI
  • Generates detailed report with scores and practical recommendations

What can you automate with the X API in 2026?

As of November 2026, the X API still lets you automate your own publishing: posts, threads made of replies to your own posts, images and video, polls and direct messages.

  • X API enables automation of self-publishing tasks as of November 2026
  • Users can post, reply, upload media, and create polls via API
  • Engagement automation (liking, following, quoting) disabled from April 16, 2026

More from Sunday 22 November →