1# Middleware Order
2 
3Middleware order is a product decision, not just a wiring detail.
4 
5A neutral production sequence is:
61. observability
72. concurrency control
83. database or storage session setup
94. idempotency
105. tenant or chat resolution
116. user loading
127. i18n setup
138. incoming message persistence
149. command or feature permissions
1510. business rules specific to the bot
1611. post-processing side effects
17 
18Why this order works:
19- observability wraps everything
20- idempotency and throttling happen before expensive business logic
21- i18n is available before handlers start rendering
22- persistence runs before downstream consumers depend on canonical message data
23- feature-specific checks happen after core context is already loaded
24 
25Use separate middleware stacks for:
26- `message`
27- `edited_message`
28- `callback_query`
29 
30Do not assume the same middleware set is correct for all update types.
31