What is a key difference between Transactional and Non-Transactional applications in OutSystems?

One of the most critical distinctions between transactional and non-transactional applications in OutSystems is rooted in how they handle data integrity. Transactional applications are designed to maintain consistency, accuracy, and reliability of data throughout the lifecycle of a transaction. This is particularly important in scenarios where multiple operations need to be completed successfully or not at all, such as in financial systems where accuracy in processing data is paramount.

Transactional applications ensure that when changes to data occur, those changes either fully complete or roll back if any part of the process fails. This ability to manage atomic operations is crucial for applications that deal with critical data operations, protecting against data corruption and ensuring that the system behaves reliably.

Non-transactional applications, on the other hand, may prioritize speed and performance over stringent data integrity controls, which makes them suitable for situations where such strictness is not required. However, this does not automatically mean they are faster or only for testing, nor that they lack user interaction. Their design generally allows for a more flexible approach to data handling.