Reading your observable state slice in a declarative fashion and instantiating/updating your component property accordingly, so you don’t have to put multiple subscribe blocks in your init function(in case you don’t want to observe it in your template) — Disclaimer: It might not be a good idea to exhaust this approach in every scenario Recently, In an imperative programming I’d been seeing this redundant patterns in our application, wherein you want to subscribe to your store state observable or some publisher$ in your component class itself. Suppose there’s a state like: