Infrastructure tooling as part of code

With containerisation solutions such as Docker, you can make the infrastructure part of your code. Most environments require some form of configuration setup to work with. With virtualisation support for cloud applications running on AWS and other cloud providers, it's become a lot easier to build/test/deploy your code on server instances which can be spun up and removed within seconds. Infrastructure as part of your code means to be able to setup a server instance without having to go through the manual process of getting all the needed OS libraries and versions figured out. You can use scripts, which can be written in a readable language, to spin an instance that has the needed setup ready for your actual application. This makes DevOps simpler for the developer who can now utilize tooling like Ansible, Puppet, Docker, and so on to provision the infrastructure when needed.

We will explore more on Docker and how to use it in practice in the next chapter. For now, here's a quick reference of a Docker file; don't worry if you haven't seen this before, we will be covering the details soon.

Take a look at the Dockerfile snippet, shown as follows:

FROM prashantp/centos-jdk:8

ADD wildfly-10.0.0.Final /opt/wildfly
EXPOSE 8080 9990
ENV WILDFLY_HOME /opt/wildfly

CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-b", "0.0.0.0"]

This is a simple sample of a Docker file that can be used to run a JBoss/Wildfly instance on your local machine.