- Hands-On Microservices with Kotlin
- Juan Antonio Medina Iglesias
- 106字
- 2021-06-30 19:10:45
Back pressure
Back pressure is produced when a reactive system is published at a rate higher than the subscriber could handle, in other words, this is how a consumer of a reactive service says: Please, I am not able to deal with the demand at the moment, stop sending data and do not waste resources (for example, buffer memory).
There is a range of mechanisms for handling this, and they are usually close to the reactive implementation, from batching the messages to dropping them, but right now, we don't need to get into the details, just understand that any reactive system must deal with back pressure.
推薦閱讀
- Learning C++ Functional Programming
- .NET 4.0面向對象編程漫談:基礎篇
- Mastering Yii
- 數據結構(C語言)
- 深度強化學習算法與實踐:基于PyTorch的實現
- 青少年學Python(第1冊)
- Swift 4從零到精通iOS開發
- Apache Camel Developer's Cookbook
- Akka入門與實踐
- C/C++代碼調試的藝術(第2版)
- Spring Boot從入門到實戰
- Socket.IO Cookbook
- Learning ROS for Robotics Programming
- 軟件再工程:優化現有軟件系統的方法與最佳實踐
- BackTrack 5 Cookbook