Now, we are really starting to make progress! Over the last three chapters, we discussed how to install GeoServer in a production environment, preparing raster data for high-performance serving; now, we looked at how we can serve vector data from an enterprise database platform.

We now have a much better understanding of what a database connection pool is and how we can optimize it for our environment. We also discussed how a servlet-container-level connection pool can be created using JNDI. We now have a better understanding of what common parameters we can set on database-backed stores such as the primary key metadata and geometry columns metadata tables.

We looked at how to create database connections, as data stores for the most common enterprise-database environments are likely to come across in production environments. We now understand how to set up GeoServer so that it can connect to Microsoft SQL Server and Oracle databases through the extension infrastructure.

Finally, we...