Paul Sturrock wrote:Without knowing your business requirements its hard to say for sure. If you can ask your business "is it OK that sometimes the application loses data, or saves data that is invalid" and they say yes, then you don't need transactions. I'd be a little surprised if this were acceptable though.
I am not sure if business knows and if they are willing to tell them about the accuracy risk as well.
Paul Sturrock wrote:Typically, multi user systems that have a small load (which is normal while developers are working on it) you can get away with quite a lot. But if you load the system lots more more errors tend to creep in, so using the application without stress testing its behaviour as a guide is probably not representative.
We did a "stress test", and ended up with a lot of failed sessions. Then we fixed the connection pool configuration, everything seems going fine now. So would that indicate we have addressed all the issues the system might have under production load?
btw, we are anticipating 200 concurrent users.