In this chapter we mostly talked about the tools to reach a Continuous Delivery process for our application management, using some tools running in the cloud. It was mainly divided into three parts; we started with Jenkins, the Continuous Integration tool, available on CloudBees. This phase checks that the application has the expected quality (statisfies all tests) independently of the host machine.

Then we saw how to use the Heroku platform to deploy a Play! Framework 2 application and took the opportunity to switch from an in-memory database to a production database—the PostgreSQL database provided by Heroku.

And finally, we introduced the Typesafe Console that will be the next killer tool for any Play! Framework 2 application, giving us a view of our application's health.

This chapter also ends the book for the pragmatic parts of Play! Framework 2.

The following chapters—appendices—will talk about where to go from here, for even more advanced use cases. Those use cases would have been far too much for the scope of this book, and would require a dedicated book in itself.

Before getting to these points, we'll also have an overview of the core concept of the Play! Framework 2—the why and how.