---
title: "Comment by Abhinav Sharma on \"Backend Ecosystem Explained Simply: Follow One Request\" | Hashnode"
description: "The split between the request path and the tools used to deploy it is helpful. It gives a beginner a way to place Docker and CI/CD in the picture without imagin"
url: "https://hashnode.com/posts/backend-ecosystem-explained-simply-follow-one-request/6adefe9d18261f3fbe423340/comment/6ae070dffe43b5b6b39e9ed2"
---

[Discussion](https://hashnode.com/posts/backend-ecosystem-explained-simply-follow-one-request/6adefe9d18261f3fbe423340)

Comment [Backend Ecosystem Explained Simply: Follow One Request](https://hashnode.com/posts/backend-ecosystem-explained-simply-follow-one-request/6adefe9d18261f3fbe423340)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 27](https://hashnode.com/posts/backend-ecosystem-explained-simply-follow-one-request/6adefe9d18261f3fbe423340/comment/6ae070dffe43b5b6b39e9ed2)

The split between the request path and the tools used to deploy it is helpful. It gives a beginner a way to place Docker and CI/CD in the picture without imagining every request travels through them.

[Stephen Muiruri](https://hashnode.com/@stephen3)

[Oct 28](https://hashnode.com/posts/backend-ecosystem-explained-simply-follow-one-request/6adefe9d18261f3fbe423340/comment/6ae070dffe43b5b6b39e9ed2#reply-6ae15e95f006f9358bc9aaa2)

Exactly! Understanding that separation makes the entire backend ecosystem easier to reason about.
