# Development Tips

**URL:** <https://community.temporal.io/t/development-tips/7555>\
**Category:** Community Support\
**Tags:** java-sdk, general-impl\
**Created:** [March 13, 2023, 9:47am UTC](https://community.temporal.io/t/development-tips/7555 "2023-03-13T09:47:07Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [March 17, 2023, 5:12pm UTC](https://community.temporal.io/t/development-tips/7555/6 "2023-03-17T17:12:24Z")

</div>

Hello @java_dev

workers are services that, as any other service, you can bundle and deploy together with other/s services or deploy isolated. To me, the preferred approach is the second one, since they might have different requirements. in addition, keep in mind that you will have to redeploy your workers (or deploy new ones with the new implementation) with any change made in the workflow code. Please see here de different versioning strategies [Workflow Versioning Strategies](https://community.temporal.io/t/workflow-versioning-strategies/6911)

> The first is in the application code, which registers itself to perform certain tasks.

I don’t understand what this means, sorry. Do you mean, deploying your workers within the microservice and calling through direct java invocations from the activities to the microservice?

Thanks,

---

_[View the full topic](https://community.temporal.io/t/development-tips/7555)._
