We have explored the Ignite memory architecture, monitored metrics, tuned performance, and secured our application. Now we are ready to deploy our code to production. Apache Ignite supports various deployment environments, such as the following:

• Docker: This is the de facto standard for packaging apps. Its a "Package Once Deploy Anywhere" [ Arun Gupta] solution for our apps. Docker allows us to package Ignite deployments with all the dependencies into a standard container.
• AWS: You can easily set up an Ignite cluster in AWS by starting an Apache Ignite machine image in EC2. AWS is a public cloud and resolves all infrastructural (scalability, security, deployment and so on) problems.
• Google Cloud: Apache Ignite machine images can be installed in Google cloud to set up a cluster and get the advantages of public cloud deployment, such as elastic scaling.
• Apache Mesos: Ignite supports scheduling and running Apache Ignite nodes in a Mesos cluster. Apache Mesos' scheduling and task management frameworks provide efficient distribution and isolation of resources and makes large-scale deployment easier.
• Kubernetes: This is an open source system for automating deployment, scaling, and management of containerized applications. Apache Ignite can be deployed in Kubernetes, it supports stateless and stateful deployment.