Ok people, after 12 months of being out of work and 20 unsuccessful interviews I'm changing tact again. I'm forever being nipped to the post by people with commercial experience, so could use a little of that myself
Here's my little task:
Couple of ideas I've come up with include: Too many requests to the database, could be resolved by splitting it? Concurrency issues, two users could be accessing the same data, user one updates it, users two is still working with the original value which no longer exists. Application could be altered to run on a server, and work with sessions.
Have people got any other ideas?
Help would be massively appreciated.

A call management application shows data about calls in a day and the ones currently in progress. This application has performance issues, the higher the amount of users, the slower it becomes. The data shown is also behind what is happening at the time, changes to the database are also sometimes lost, UI will occasionally freeze.
Architecture wise, there is a database, application on each users computer, and a windows service calculating the calls.
Architecture wise, there is a database, application on each users computer, and a windows service calculating the calls.
Have people got any other ideas?

Comment