In this episode of Appian Rocks, host Stefan is joined by Sandro, Marcel, and special guest Joe Longworth to discuss the pros and cons of using database tasks versus process tasks in the Appian platform. The conversation was sparked by a discussion on a Discord server where Joe shared his extensive experience with running large applications involving hundreds of thousands of users and tasks. Joe’s preference for database tasks over Appian's built-in process tasks led to an in-depth discussion about the design considerations and challenges associated with each approach. Joe explains that one of the main drivers for his decision to use database tasks is security and the complexity of managing Appian groups. In large deployments with tens of thousands of clients and numerous dimensions of security, using Appian groups can become unmanageable. Joe points out that assigning tasks to groups in Appian can lead to a situation where hundreds of thousands of groups are needed, making it difficult to manage users and their permissions. By contrast, using database tasks allows for more flexible and scalable management of task assignments based on attributes stored in the database. Stefan and Marcel also share their perspectives on the topic. Stefan prefers using Appian tasks for their simplicity and built-in features, which are sufficient for many use cases. However, he acknowledges that for large-scale deployments or scenarios requiring complex security and task management, database tasks may be the better option. Marcel adds that while database tasks offer advantages in terms of scalability and flexibility, they also require more development effort and a higher level of technical expertise. Joe provides insights into his background and experience with Appian, having worked with the platform since 2011. He currently leads a team that manages a large environment with around 10 million active tasks and a user base of 3,500 internal and 200,000 external users. Joe emphasizes the importance of scalability and performance in his decision to use database tasks, as well as the need to integrate with third-party systems and manage tasks completed outside of Appian. The discussion also touches on the challenges of implementing database tasks, such as building custom features like task notifications and managing task reassignment. Joe highlights the benefits of database tasks, including the ability to restart tasks easily and the flexibility to aggregate and work on multiple tasks simultaneously. He also notes that database tasks can simplify the process of upgrading and changing processes, as they are not tied to specific process instances. The episode concludes with a summary of the key considerations for choosing between database tasks and Appian tasks. Factors such as the number of tasks, the complexity of security requirements, the need for integration with external systems, and the distribution of tasks over time should all be taken into account. The hosts agree that while Appian's built-in tasks are suitable for many scenarios, database tasks offer significant advantages for large-scale and complex deployments. Overall, the episode provides valuable insights into the decision-making process for task management in Appian, highlighting the trade-offs and benefits of each approach. The conversation underscores the importance of understanding the specific requirements and constraints of a project to make an informed decision.