Deployment Options
Apache Ignite can run stand alone, in a cluster, within Kubernetes and Docker containers, as well as on Apache Mesos and Hadoop Yarn. It can also run on physical servers as well as within virtual environments.
For public cloud environments, Ignite has native integration with Amazon AWS
and Google Compute Engine
. For all other cloud environments, Ignite
integrates with Apache JClouds
that has support for most of the
existing
cloud providers.
Ignite can freely run within container environments. Ignite's integration with Docker
allows to automatically build and deploy user code into Ignite prior to server startup.
Apache Ignite cluster can also be deployed in Kubernetes
that allows automatic deployment and management of
containerized applications.
Ignite provides native integration for Hadoop Yarn
and Apache Mesos
making it very easy
to seamlessly deploy Ignite into Hadoop and Spark environments.
Deployment Options
Feature | Description |
---|---|
Zero Deployment |
Ignite nodes automatically become aware of custom classes, eliminating the need to explicitly deploy them. |
Dynamic Schema Changes |
Ignite stores objects in binary format eliminating the need to deploy classes on server nodes. |
Stand-Alone Clusters |
Ignite nodes can automatically discover each other. This helps to scale the cluster when needed, without having to restart the whole cluster - simply start up new additional nodes and they will automatically join the existing work loads. |
Docker Container |
|
Kubernetes |
Apache Ignite cluster can be easily deployed in and maintained by |
Public Clouds |
For public cloud environments, Ignite has native integration with |
Apache Mesos |
Ignite provides native integration for |
Hadoop Yarn |
Ignite provides native integration for |
OSGI Support |