# Best Practice - Messaging vs Input Properties for communication between components

**URL:** <https://forum.inductiveautomation.com/t/best-practice-messaging-vs-input-properties-for-communication-between-components/95085>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [August 23, 2024, 3:21pm UTC](https://forum.inductiveautomation.com/t/best-practice-messaging-vs-input-properties-for-communication-between-components/95085 "2024-08-23T15:21:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mal](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@mal](https://forum.inductiveautomation.com/u/mal)\
**Post date:** [August 23, 2024, 3:21pm UTC](https://forum.inductiveautomation.com/t/best-practice-messaging-vs-input-properties-for-communication-between-components/95085/1 "2024-08-23T15:21:47Z")

</div>

My team and I have been having discussions on messaging vs input properties to pass data and actions between components. We have been passing data down via bindings + input properties and passing data back up via messaging. We had a situation where the type of action that passed data down to the sub-component mattered to the subcomponent, IE whether the sub-component needed to refresh due to the pass-down. We decided on passing down the action via messaging, breaking our flow. This has led to discussions on what is the best practice? And what are other people doing?