# Message Listeners in Ions

**URL:** <https://forum.datomic.com/t/message-listeners-in-ions/860>\
**Category:** Datomic Cloud\
**Created:** [February 25, 2019, 7:22pm UTC](https://forum.datomic.com/t/message-listeners-in-ions/860 "2019-02-25T19:22:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marshall](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/marshall/32/48_2.png) [@marshall](https://forum.datomic.com/u/marshall)\
**Post date:** [February 26, 2019, 2:12pm UTC](https://forum.datomic.com/t/message-listeners-in-ions/860/2 "2019-02-26T14:12:32Z")

</div>

You can certainly have a background thread that runs on your Datomic node(s) and handles async processing.

See [Kafka Consumer as an Ion?](https://forum.datomic.com/t/kafka-consumer-as-an-ion/823/4?u=marshall)

The main point I should make here is that your process should be coordinated via ion calls, but you should not make individual ion calls that are long-lived (i.e. don’t make `run-my-whole-import-job` a lambda-invoked ion).

---

_[View the full topic](https://forum.datomic.com/t/message-listeners-in-ions/860)._