# View Hotel

Name:
#{hotel.name}
Address:
#{hotel.address}
City:
#{hotel.city}
State:
#{hotel.state}
Zip:
#{hotel.zip}
Country:
#{hotel.country}
Nightly rate:

# Don't kill your database

Keeping conversational state in memory in the middle tier is a great way to improve your application's scalability. It saves hitting the database every time we refresh a page, to re-read the data we were just looking at five seconds ago. By using Seam's conversation context, we get a natural cache of data associated with the what the user is currently doing. By nature, this cache has a more efficient eviction policy than the MRU-type algorithms used by a typical second-level data cache in an O/R mapping engine like Hibernate (at least for some kinds of data). Of course, you should use a clever combination of second-level caching and conversational data caching to achieve the best performance for your application.