---
title: "Discussion on \"NVIDIA Dynamo vs KServe: Which Layer Should Own Your LLM Inference?\" | Hashnode"
description: "Discussion on \"NVIDIA Dynamo vs KServe: Which Layer Should Own Your LLM Inference?\". Cache-aware routing, prefill/decode disaggregation and autoscaling compared, and how to choose per model pool"
url: "https://hashnode.com/posts/nvidia-dynamo-vs-kserve-which-layer-should-own-your-llm-inference/6ad6439fa7db020af3c69de6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [NVIDIA Dynamo vs KServe: Which Layer Should Own Your LLM Inference?](https://blog.shubhamtatvamasi.com/nvidia-dynamo-vs-kserve-which-layer-should-own-your-llm-inference?utm_source=hashnode&utm_medium=feed)

Cache-aware routing, prefill/decode disaggregation and autoscaling compared, and how to choose per model pool

Oct 19 · 13 min read · blog.shubhamtatvamasi.com  
Updated Oct 25  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#llm](https://hashnode.com/tag/llm)
-   [#nvidia](https://hashnode.com/tag/nvidia)
-   [#mlops](https://hashnode.com/tag/mlops)
-   [#ai](https://hashnode.com/tag/ai)

## Written by

[Shubham Tatvamasi](https://hashnode.com/@ShubhamTatvamasi)

@ShubhamTatvamasi

  
[View profile](https://hashnode.com/@ShubhamTatvamasi)

AI infrastructure engineer. Inference, GPUs and GitOps on Kubernetes.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
