Willie Wheeler
Willie Wheeler
Want to capture flow related metrics: - records consumed - records produced - time delay (processing lag)
@bibinss Can I let you fill in the details here please?
Currently it is very easy for a change to break the Kafka apps. For example when I moved a Spring Boot-based Kafka app into the `kafka` module, it broke the...
Currently this is hardcoded as a JsonPojoSerde. This should be configurable.
The Scala e2e test in the Kafka module is currently ignored and probably doesn't work as we haven't been maintaining it. We would like it to work.
The way the haystack-commons health check works is that when an uncaught exception occurs in Kafka, the health controller would write to a file indicating that the app is unhealthy,...
Idea is that we want to separate client-induced exceptions (like rate limit exceptions, concurrency exceptions) from others so we can ensure that the circuit breaker doesn't trip on client exceptions.
We may want to limit requests to a specific time window. It may be for example that we want to ensure that expensive requests happen only during low-volume times.
Given that hypermedia APIs can be on the chatty side, HTTP keepalive would be a useful feature from a performance perspective. It doesn't look like hyperresource currently supports this. Consider...