Data API Builder 1.6 Adds HTTP Header Controls and Flexible Logging

"Microsoft has released Data API Builder (DAB) 1.6, expanding the open-source runtime's capabilities for REST and GraphQL endpoints over Azure SQL, PostgreSQL, MySQL, and Cosmos DB. The new version introduces advanced HTTP header behaviours for better client-side control and a revamped logging subsystem designed to improve diagnostics and observability in both cloud and on-premise deployments. Data API Builder provides a stateless middle layer that automatically exposes database objects as secure REST API endpoints."

"However, general developer feedback from social networks indicates that DAB is suited only for prototyping and simple scenarios. As one developer mentions on Reddit, it lacks validations with custom business logic, updates over multiple entities, and custom error handling. Version 1.6 continues Microsoft's focus on production readiness by addressing two main areas: header semantics and runtime telemetry. According to Microsoft's DevBlogs announcement, Data API Builder 1.6 now honours standard HTTP headers that control how clients interact with exposed data entities:"

"The release also introduces a new logging system that replaces the static configuration model from earlier versions. Developers can now define multiple sinks and log levels using JSON configuration or environment variables, supporting tailored observability for local debugging or cloud production: File sink for writing structured logs to disk, suitable for local or containerised deployments. Azure Log Analytics and Application Insights sinks for centralis"

Data API Builder 1.6 expands runtime support for REST and GraphQL endpoints across Azure SQL, PostgreSQL, MySQL, and Cosmos DB. The release adds advanced HTTP header behaviours to give clients finer control over interactions with exposed data entities, improving interoperability with HTTP clients, reverse proxies, and API gateways. The runtime remains a stateless middle layer that exposes database objects as secure REST API endpoints, aimed at accelerating backend development. The new logging system replaces static configuration and allows multiple sinks and log levels via JSON or environment variables, supporting file logs, Azure Log Analytics, and Application Insights. ETag generation and full conditional request support remain planned for a future release.

Read at InfoQ