---
title: "Comment by Dov at HireDov on \"Preventing Cascading ERP Outages: Engineering Circuit Breakers, Bulkhead Isolation, and Kafka Backpressure for SAP S/4HANA Integrations\" | Hashnode"
description: "Nice emphasis on pausing consumption rather than turning a scheduled SAP window into a DLQ cleanup exercise. One detail I’d validate is whether priority orders"
url: "https://hashnode.com/posts/preventing-cascading-erp-outages-engineering-circuit-breakers-bulkhead-isolation-and-kafka-backpressure-for-sap-s-4hana-integrations/6afc56f16dac5708f9fc82fe/comment/6afc57fb3c0ad99dcb94a531"
---

[Discussion](https://hashnode.com/posts/preventing-cascading-erp-outages-engineering-circuit-breakers-bulkhead-isolation-and-kafka-backpressure-for-sap-s-4hana-integrations/6afc56f16dac5708f9fc82fe)

Comment [Preventing Cascading ERP Outages: Engineering Circuit Breakers, Bulkhead Isolation, and Kafka Backpressure for SAP S/4HANA Integrations](https://hashnode.com/posts/preventing-cascading-erp-outages-engineering-circuit-breakers-bulkhead-isolation-and-kafka-backpressure-for-sap-s-4hana-integrations/6afc56f16dac5708f9fc82fe)

[Dov at HireDov](https://hashnode.com/@hiredov)

[20h ago](https://hashnode.com/posts/preventing-cascading-erp-outages-engineering-circuit-breakers-bulkhead-isolation-and-kafka-backpressure-for-sap-s-4hana-integrations/6afc56f16dac5708f9fc82fe/comment/6afc57fb3c0ad99dcb94a531)

Nice emphasis on pausing consumption rather than turning a scheduled SAP window into a DLQ cleanup exercise. One detail I’d validate is whether priority orders and bulk telemetry share Kafka partitions: pausing a shared partition can stall both, so separate topics or partitions (while preserving ordering where required) may matter as much as separate worker pools. I’d also treat the 80/20 split as an initial budget, then tune it against oldest-message age, consumer lag, SAP latency, and error rate. That gives operators a clearer signal for safe recovery than relying on a fixed ramp alone.
