Microsoft adds HorizonDB to Fabric to ease development of agent-driven applications
InfoWorld ·

Microsoft is adding a serverless flavor of HorizonDB to its data and analytics platform, Fabric, to make it easier for developers, business teams and AI agents to build intermittently used applications for automating business workflows and supporting agent-driven tasks. The hyperscaler first unveiled HorizonDB for Azure at its Ignite conference in November 2025, positioning it as a PostgreSQL -compatible database for demanding enterprise workloads, including mission-critical applications that require high performance and scalability. Its architecture, according to Microsoft, combines shared storage with elastic, scale-out compute to support the performance and scalability that large databases and transaction-heavy workloads require. The new flavor, named Fabric HorizonDB , which was launched in public preview at this year’s ongoing Ignite conference, by contrast, targets smaller workloads that do not require continuously running database infrastructure. It provides a managed backend that automatically provisions and scales databases based on demand, pausing them when idle and resuming them when needed, the hyperscaler wrote in a blog post . It also lets applications query live transactional data alongside analytical data in OneLake through a single PostgreSQL interface, reducing the infrastructure and data integration work involved in building applications, it added. In order to support translytical queries, Fabric HorizonDB uses Fabric Data Warehouse’s distributed compute to execute supported analytical portions of PostgreSQL queries across CPU- and GPU -powered resources, while retaining transactional processing in its PostgreSQL engine, it further wrote. New database could reduce engineering effort Analysts, too, see Fabric HorizonDB’s serverless and translytical capabilities helping developers simplify the development of agent-driven applications. “Agent-driven applications often need to spin up databases on demand to support specific tasks and workflows. Fabric HorizonDB makes this easier by allowing developers and AI agents to provision databases quickly without having to manually set up separate backend services for workloads that may be short-lived,” said David Linthicum , an independent technology consultant. “That reduces the friction between an idea, its implementation as an application, and the data needed to make it work,” Linthicum added. Similarly, the translytical capabilities also reduce engineering effort, according to Ashish Chaturvedi , executive research leader at HFS Research. “Previously, querying operational and transactional data together required engineering effort, usually involving a pipeline or connector that teams had to build, secure and maintain. Microsoft has turned that into a built-in capability, allowing an application to retrieve a customer’s current order and purchase history in a single request,” Chaturvedi said. Lower engineering effort could help CIOs scale applications CIOs, too, benefit from the reduced engineering effort, Chaturvedi pointed out. “As developers spend less time building and maintaining data integration pipelines and more time developing applications, it shortens development cycles, improves engineering productivity and makes it easier for enterprises to scale agent-driven applications across business functions,” Chaturvedi said. The bigger value for CIOs lies in simplification, Linthicum said. “The new database can reduce the number of platforms, pipelines, and teams required to connect applications with enterprise data. If Microsoft executes well, CIOs get less integration debt, better use of Fabric investments, and a clearer path from operational systems to analytics and AI.” Beyond infrastructure and productivity gains, the ability to combine operational and historical data could also improve business decision-making, Chaturvedi pointed out. “Mainly because they can draw on live operational data and historical business information together, rather than relying on either in isolation. This allows applications and AI agents to factor in current business activity as well as historical patterns when evaluating situations and recommending actions,” Chaturvedi said. These could include sales applications that show a customer’s open issues alongside their lifetime value, or AI agents that use current business information and historical trends to make recommendations, Chaturvedi added. In addition, Fabric HorizonDB’s serverless model could also help CIOs control the costs of running the growing number of applications generated by AI agents. “Every new application needs a database to store and manage its data, and provisioning dedicated infrastructure for each one can quickly add to costs and operational complexity,” Chaturvedi said. Since Fabric HorizonDB automatically pauses its compute after five consecutive minutes of eligible inactivity, a prototype or a rarely used internal tool costs very little while it sits idle, Chaturvedi added. Cold starts, data freshness among trade-offs Despite these advantages, Fabric HorizonDB’s architecture could introduce trade-offs, analysts pointed out. “Serverless is attractive, but it often introduces cold-start latency, scaling lag, and less predictable performance than provisioned infrastructure,” Linthicum said. Developers should test how the database handles pause-and-resume operations, concurrent requests, and transaction-heavy workloads, he added. These performance characteristics could limit the types of applications suited to the database, Chaturvedi said. “The brief wait when a database resumes after being idle is fine for internal tools and occasional workloads, but less suitable for customer-facing systems that need consistent response times.” Data freshness is also another consideration since the analytical copy in OneLake updates with a slight delay, Chaturvedi said. That makes translytical queries more suitable for applications that can tolerate data that is a few moments old than those requiring strictly real-time consistency, he added. There are also questions around portability and dependence on Microsoft’s ecosystem. While PostgreSQL compatibility provides developers with a familiar database interface, applications that rely on Fabric-specific services, OneLake, or translytical capabilities could be harder to move to other platforms, Linthicum cautioned. Beyond portability, the ease of developing applications could create new governance challenges for CIOs, said Stephanie Walter , practice leader of AI stack at HyperFrame Research. “CIOs will need visibility into costs across database compute, storage and analytical queries, including which charges continue when database compute is paused,” Walter said.