Book Image

Play Framework Cookbook

By : Alexander Reelsen
Book Image

Play Framework Cookbook

By: Alexander Reelsen

Overview of this book

<p>The Play framework is the new kid on the block of Java frameworks. By breaking with existing standards the play framework tries not to abstract away from HTTP as most web frameworks do, but tightly integrates with it. This means quite a shift for Java programmers. Understanding these concepts behind the play framework and its impact on web development with Java are crucial for fast development of applications.<br /><br />The Play Framework Cookbook starts where the beginner documentation ends. It shows you how to utilize advanced features of the Play framework &ndash; piece by piece and completely outlined with working applications!<br /><br />The reader will be taken through all layers of the Play Framework and provided with in-depth knowledge from as many examples and applications as possible. Leveraging the most from the Play framework means to think simple again in a java environment. Implement your own renderers, integrate tightly with HTTP, use existing code, improve site performance with caching and integrate with other web services and interfaces. Learn about non-functional issues like modularity or integration into production and testing environments. In order to provide the best learning experience during reading Play Framework Cookbook, almost every example is provided with source code, so you can start immediately to integrate recipes into your own play applications.</p>
Table of Contents (16 chapters)
Play Framework Cookbook
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
Further Information About the Play Framework
Index

Implementing own monitoring points


As soon as you experience the first performance bottleneck in your application, there are two steps to carry out: analyze the problem and fix it. If you application design is not completely flawed, fixing usually takes a fraction of the time needed for analyzing. The analysis is split in two parts. Finding the occurrence of the problem in your platform and reproducing the problem reliably in order to fix it. Most likely problems will occur on production because real live problems will never be completely found by lab testing.

After you have fixed the problem, hopefully the operations department or even you would raise the rhetorical question about making sure this does not happen again. The answer is simple: Monitoring. You should always be able to return reliable statistics from the core of the application instead of relying on external measuring points such as database query times or HTTP request and response times.

There should be data about cache hit...