A Mule application currently writes to two separate SQL Server database instances across the internet using a single XA transaction. It is proposed to split this one transaction into two separate non-XA transactions with no other changes to the Mule application.
What non-functional requirement can be expected to be negatively affected when implementing this change?
When splitting a single XA transaction into two separate non-XA transactions, consistency is the non-functional requirement most likely to be negatively affected. This is because XA transactions are designed to ensure that all parts of a distributed transaction either commit or roll back together, maintaining a consistent state across multiple resources. By splitting a single XA transaction into two non-XA transactions, there is a risk that one transaction could commit while the other fails, leading to an inconsistent state between the two database instances.
D, without transactions, consistency will be impacted
Answer is D
D. Consistency