Chapter 7. Dealing with state
This chapter covers
- Configuring Play for an optimal connection to a relational database, and accessing the database with jOOQ
- Creating custom requests and actions and using them with the client-side session
- Command and Query Responsibility Segregation and Event Sourcing (CQRS/ES)
One of the biggest practical hurdles of switching from a traditional application-server development model to a scalable model such as Play is solving the problem of working with state in a stateless architecture. The server-side deployment of a Play application is meant to be stateless—it doesn’t keep any state in memory other than that for the requests currently being processed. This is in keeping with the philosophy of reactive ...
Get Reactive Web Applications now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
