Marcus Delacroix-Hwang

Agents need isolated data environments to explore safely without risking production.

Measure data freshness, completeness.

Database isolation requirements protect against agent-driven blast radius, not just access scope.

Scan patterns and concurrent queries signal when analytical work belongs in a separate store.

Query planners go blind when foreign functions enter analytical database plans.

Pick the model that matches your latency requirement, not the one that sounds more sophisticated.

Consumption-based OLAP pricing shifts financial risk from vendors to customer budgets.

Consumption pricing works best for bursty workloads, flat pricing for high utilization.

Hidden data transfer costs undermine the clean billing promise of separated architectures.