Is there any way create a middleware between controller and service ?

[pulsar ice]

Hi, I know there is Middleware that applied between route handler and controllers but is there any way to create a middleware between controller and service in Nest ?

[arctic stump]

Suggestion for @pulsar ice:
Nest applications handle requests and produce responses in a sequence we refer to as the request lifecycle.
With the use of middleware, pipes, guards, and interceptors, it can be challenging to track down where a particular piece of code executes during the request lifecycle, especially as global, controller level, and route level components come into play.
In general, a request flows through middleware to guards, then to interceptors, then to pipes and finally back to interceptors on the return path (as the response is generated).

1. Incoming request
2. Globally bound middleware
3. Module bound middleware
4. Global guards
5. Controller guards
6. Route guards
7. Global interceptors (pre-controller)
8. Controller interceptors (pre-controller)
9. Route interceptors (pre-controller)
10. Global pipes
11. Controller pipes
12. Route pipes
13. Route parameter pipes
14. Controller (method handler)
15. Service (if exists)
16. Route interceptor (post-request)
17. Controller interceptor (post-request)
18. Global interceptor (post-request)
19. Exception filters (route, then controller, then global)
20. Server response

[dull plover]

middleware between controller and service in Nest
nop
that doesn't fits the concept of middleware