| extend ../_components/base.pug |
| |
| block pagetitle |
| | Deployment Options |
| |
| block css |
| link(rel="stylesheet", href="../css/native-persistence.css") |
| link(rel="stylesheet", href="../css/deployment-opts.css") |
| |
| |
| |
| block main |
| - global.pageHref = "features" |
| - config.hdrClassName = "hdr__blue" |
| include ../_components/header.pug |
| |
| |
| section.innerhero |
| .container.innerhero__cont |
| .innerhero__main |
| .innerhero__pre.pb-3 Apache Ignite |
| h1.h1.innerhero__h1.innerhero__mega Deployment <br>Options |
| img.innerhero__pic.innerhero__pic--deploy(src="/public/img/features/deployment/hero.svg", alt="Deployment Options") |
| // /.innerhero |
| |
| |
| section.deploymenytext.container.flexi |
| .deploymenytext__main |
| p Apache Ignite® implements the shared-nothing architecture where all cluster nodes are equal and there is no single point of failure or bottleneck. Ignite does NOT have a component such as a master node or name node that is present in most distributed systems. |
| |
| p Ignite nodes discover each other automatically in your environment, and the cluster can be scaled out or in easily. |
| |
| p.pb-4 Apache Ignite can run on bare metal, virtual machines, Docker, Kubernetes, and cloud environments. Technically there are no limitations in regards to deployment environments — since Ignite nodes can auto-discover each other via the TCP/IP interface, you can launch a cluster anywhere. |
| |
| h3.h5.pt-2.pb-2.deploymenytext__title Servers, clients and protocols |
| p Ignite defines two types of nodes — servers and clients. A server node is the base computational and data storage unit. Typically, you start a single server node per machine or container and it will scale vertically by utilizing all of the CPU, RAM, and other resources available unless specified differently. These resources are pooled and become available to Ignite applications once the server node joins the cluster of other server nodes. |
| |
| p A cluster is a group of server nodes interconnected together in order to provide shared resources like RAM and CPU to your applications. |
| |
| p Client nodes (aka. thick clients) are your connection endpoints and gateways from the application layer to the cluster of server nodes. You always embed a client into your application code and execute the required APIs. The clients shield all the complexity of Ignite’s distributed nature from application developers who will see the cluster as a single unit. It’s as simple as connecting to an RDBMS via a JDBC driver or Spring Data framework. |
| |
| p In addition to the thick clients, you can access the cluster with Ignite thin clients, JDBC and ODBC drivers, or the REST API. |
| |
| |
| aside.deploymenytext__picwrap.picwrap |
| img.deploymenytext__pic(src="/public/img/features/deployment/deploy-pic.svg", alt="") |
| |
| |
| section.native-bottom.container |
| .native-bottom__grid |
| article.nativebotblock |
| h3.h4.nativebotblock__title |
| img(src="/public/img/features/native-rocket.svg", alt="").nativebotblock__icon |
| span Ready to Start? |
| p.nativebotblock__text Discover more details about multi-tier storage <br>and configure it for your use-case |
| a.nativebotblock__link.arrowlink(href="https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood", target="_blank") Working with SQL Guide |
| article.nativebotblock.nativebotblock--learn |
| h3.h4.nativebotblock__title |
| img(src="/public/img/features/native-docs.svg", alt="").nativebotblock__icon |
| span Want to View More Use-Cases? |
| p.nativebotblock__text Check out success stories from different industries across the world |
| a.nativebotblock__link.arrowlink(href="https://ignite.apache.org/docs/latest/persistence/native-persistence", target="_blank") Multi-Tier Storage Implementation Details |
| |
| |
| |
| |
