Pros and cons in using multiple actor types in same Service Fabric service

Question

When using the Azure Service Fabric Reliable Actor programming model, what are the pros and cons of using several actor types in the same service? Is it only a matter of deployment, or are there runtime considerations as well?

Answer 1

Pros:

• Increases density.
• Fewer projects to manage which is always helpful.

Cons:

• The actor types within the same package will have to be deployed/upgraded at the same time and are no longer independent.

My advice would be to use the same code packages if the various actors are quite tightly coupled logically.