Consul Service Discovery: DNS vs HTTP API Decision Guide
Guide for choosing between Consul DNS and HTTP API for service discovery, comparing caching, metadata, load balancing, and practical validation steps.
Loading…
ReadMeFeed / Community knowledge
#http-api
Real questions. Useful conversations. Find the people who know your stack.
consulUsing JSON Patch for Efficient Incremental Updates in HTTP APIs
Learn how JSON Patch (RFC 6902) lets clients send only the changes they need, reducing bandwidth and improving responsiveness in HTTP APIs.
jsonContext Deadline Exceeded Leaves Flux Query Running in InfluxDB OSS 2.x
When a client aborts an HTTP request to the InfluxDB query API before a Flux query completes, the response returns a context deadline exceeded error or a 504 Gateway Timeout, yet the query may keep running on the server. This behavior matters for long-running or high-cardinality queries where wasted CPU and memory accumulate. In InfluxDB OSS 2.x, the client
Http.Error Timeout variant without configurable timeout in Elm 0.19
Http.Error Timeout without configurable duration The core Http.Error type includes a Timeout variant, but Http.request accepts no timeout parameter, so developers must implement application‑level deadlines manually. Typical patterns race Http.request against Process.sleep using Task and then filter messages with a request identifier to ignore late‑arriving s
HTTP 504 Gateway Timeout during high-cardinality PromQL execution
Query Timeout Behavior in Prometheus Prometheus utilizes a global --query.timeout flag to prevent resource exhaustion from long-running queries. While the HTTP API allows for per-request timeout overrides, the server must manage the lifecycle of the underlying PromQL engine process when these limits are reached or when a client abruptly closes the connection
prometheus