In this chapter, you learned and analyzed the application Ticket Monster on two different application architectures and how to install the application locally.

We discussed and presented various types of classes and how they are separated in different layers. We have seen in detail the use cases for users and the administration profile, and how to use JBoss Forge to create the administration UI.

Then we moved on to discuss architecture and design in two different scenarios, a traditional architecture with a database approach, and another architecture contemplating Infinispan.

After that, we presented new requirements related to performance, where we discussed different solutions to scale the Ticket Monster application.

We discussed the issues in distributed web application, three patterns to store session state, and how to apply them to solve these issues.

Finally, we presented how to implement Infinispan involving the current architecture.

In the next chapter, you will learn in detail...