Performance? That’s what version 2 is for!
Despite the widespread recognition that performance is important to the success of a project, many software products fail to respond fast enough to user requests or to handle a certain amount of parallel business transactions.
Reasons for that can be insufficiently or not defined performance goals and the fact that performance is addressed late in an application’s lifecycle and usually only after performance issues are discovered. Memory leaks, poor response times, timeouts, concurrency and scaling issues, or caching problems are only a few examples that occur when an application is put to production and exposed to real users.
The first part covers the importance and the necessity of performance in nowadays software projects and shows what the consequences could be when having a poor performing application. The second part dives into different architectural layers of a usual software application and shows where performance issues can reside and which impact they can have. In addition to that, various possibilities are presented in order to tackle and prevent possible performance issues before an application reaches its production stage.