---
title: "Comment by Azhar Abbas on \"Managed Services Won't Save You From Your Own Code\" | Hashnode"
description: "Good reminder that a managed service only protects the infrastructure layer, not how your code uses it. A per-request memory cap, pagination or streaming for la"
url: "https://hashnode.com/posts/managed-services-won-t-save-you-from-your-own-code/6af750b29f0a9eb118bc7fd0/comment/6af80fdbd39700cb746c41bf"
---

[Discussion](https://hashnode.com/posts/managed-services-won-t-save-you-from-your-own-code/6af750b29f0a9eb118bc7fd0)

Comment [Managed Services Won't Save You From Your Own Code](https://hashnode.com/posts/managed-services-won-t-save-you-from-your-own-code/6af750b29f0a9eb118bc7fd0)

[Azhar Abbas](https://hashnode.com/@azharabbas)

[1d ago](https://hashnode.com/posts/managed-services-won-t-save-you-from-your-own-code/6af750b29f0a9eb118bc7fd0/comment/6af80fdbd39700cb746c41bf)

Good reminder that a managed service only protects the infrastructure layer, not how your code uses it. A per-request memory cap, pagination or streaming for large result sets, and an alert on memory per process (not just per host) usually catch this kind of bug before it takes the whole server down. Thanks for walking through the incident.