# confd\_trans\_cbs trans\_cbs\_ and multiple confd\_trans\_cbs data\_cbs\_

**URL:** <https://dmap-community.ductus.global/t/confd-trans-cbs-trans-cbs--and-multiple-confd-trans-cbs-data-cbs-/410>\
**Category:** CDB and CDB API\
**Created:** [March 9, 2016, 9:08am UTC](https://dmap-community.ductus.global/t/confd-trans-cbs-trans-cbs--and-multiple-confd-trans-cbs-data-cbs-/410 "2016-03-09T09:08:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![poornima11](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@poornima11](https://dmap-community.ductus.global/u/poornima11)\
**Post date:** [March 9, 2016, 9:08am UTC](https://dmap-community.ductus.global/t/confd-trans-cbs-trans-cbs--and-multiple-confd-trans-cbs-data-cbs-/410/1 "2016-03-09T09:08:43Z")

</div>

I have several call-points for operational data defined in the YANG. To set the fields, I have registered only one transaction callback and multiple data callbacks. Does it have any performance impact?

Best regards,  
Poornima.M

---

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [March 9, 2016, 11:48am UTC](https://dmap-community.ductus.global/t/confd-trans-cbs-trans-cbs--and-multiple-confd-trans-cbs-data-cbs-/410/2 "2016-03-09T11:48:37Z")

</div>

Having one transaction callback is a good choice. Keeping the data callbacks separate makes sense unless you have very similar data to return, and into minimising the footprint.  
See more on this subject in the ConfD UG Chapter “The Protocol and a Library Threads Discussion” to select the best design for your particular use-case.