In this chapter we utilized Spring Python's convenient transactional features in order to turn some simple banking SQL into a resilient application. Being able to pick between the easy-to-read @transactional decorator and an AOP-based TransactionProxyFactoryObject gives us flexible choices.
In this chapter we have learned that:
The classic transaction issue makes coding transactions by hand difficult
Spring Python lets us easily add transactions to a banking application using the @transactional decorator
We can easily code transactions programmatically with and without the IoC container, giving us the maximum in choices
With the power of AOP, we can non-intrusively mix in transactions to non-transactional code without editing the source
In the next chapter, we will explore ways to secure, web applications using Spring Python security module.