Most of our Quarkus endpoints follow the standard practice in which they’re annotated with @Transactional, call into our business layer, and if an exception is thrown the entire transaction is rolled back.