---
title: "Comment by MadhusudhanG on \"Understanding Sling: Resource Resolution & Request Lifecycle\" | Hashnode"
description: "Sling's resource-first model feels unusual if you come from controller-based frameworks. What was your \"aha\" moment with resource types and selectors, or what's"
url: "https://hashnode.com/posts/understanding-sling-resource-resolution-request-lifecycle/6aa5545910d69d421e642c07/comment/6adf4376f2d63d3f7ac41e1c"
---

[Discussion](https://hashnode.com/posts/understanding-sling-resource-resolution-request-lifecycle/6aa5545910d69d421e642c07)

Comment [Understanding Sling: Resource Resolution & Request Lifecycle](https://hashnode.com/posts/understanding-sling-resource-resolution-request-lifecycle/6aa5545910d69d421e642c07)

[MadhusudhanG](https://hashnode.com/@madhusudhan-aem)

[Oct 26](https://hashnode.com/posts/understanding-sling-resource-resolution-request-lifecycle/6aa5545910d69d421e642c07/comment/6adf4376f2d63d3f7ac41e1c)

Sling's resource-first model feels unusual if you come from controller-based frameworks. What was your "aha" moment with resource types and selectors, or what's still confusing?
