How many Activities should I use in my Temporal Workflow?

This post provides detailed guidance on designing Temporal Activities, focusing on the trade-offs between using many fine-grained Activities versus fewer coarse-grained ones. It outlines specific scenarios where splitting work into multiple Activities is necessary (e.g., routing to different task queues for specialized hardware or security, distinct retry/timeout policies) or practical (e.g., multiple database transactions, external state-changing API calls, cost optimization, dynamic execution, detailed observability). The core recommendation is to aim for one operation per Activity to enhance maintainability, observability, and reliability, while providing clear reasoning for exceptions.